diff options
author | Explorer09 <explorer09@gmail.com> | 2016-01-15 20:26:01 +0800 |
---|---|---|
committer | Explorer09 <explorer09@gmail.com> | 2016-01-15 20:26:01 +0800 |
commit | 6dae8108f8e6a8d3f4ccf3d92f8bb19d3933861a (patch) | |
tree | 7cb08e282337b483de387b68cf7e225eb359853f /RichString.c | |
parent | 195f5edbc8dd79267fa23feb5fda2a8be812abeb (diff) |
Introduce CLAMP macro. Unify all MIN(MAX(a,b),c) uses.
With the CLAMP macro replacing the combination of MIN and MAX, we will
have at least two advantages:
1. It's more obvious semantically.
2. There are no more mixes of confusing uses like MIN(MAX(a,b),c) and
MAX(MIN(a,b),c) and MIN(a,MAX(b,c)) appearing everywhere. We unify
the 'clamping' with a single macro.
Note that the behavior of this CLAMP macro is different from
the combination `MAX(low,MIN(x,high))`.
* This CLAMP macro expands to two comparisons instead of three from
MAX and MIN combination. In theory, this makes the code slightly
smaller, in case that (low) or (high) or both are computed at
runtime, so that compilers cannot optimize them. (The third
comparison will matter if (low)>(high); see below.)
* CLAMP has a side effect, that if (low)>(high) it will produce weird
results. Unlike MIN & MAX which will force either (low) or (high) to
win. No assertion of ((low)<=(high)) is done in this macro, for now.
This CLAMP macro is implemented like described in glib
<http://developer.gnome.org/glib/stable/glib-Standard-Macros.html>
and does not handle weird uses like CLAMP(a++, low++, high--) .
Diffstat (limited to 'RichString.c')
-rw-r--r-- | RichString.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/RichString.c b/RichString.c index c9c02dec..75198330 100644 --- a/RichString.c +++ b/RichString.c @@ -62,10 +62,6 @@ typedef struct RichString_ { }*/ -#ifndef MIN -#define MIN(a,b) ((a)<(b)?(a):(b)) -#endif - #define charBytes(n) (sizeof(CharType) * (n)) static void RichString_extendLen(RichString* this, int len) { |