[lkml]   [2001]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: macro conflict
There has already been **much** discussion about this, but I think
that the bottom line is that the new version is safer and more
robust than the old version, and thus is not likely to be changed

Consider what happens if someone writes min(++x,y) - the old
version expands to (without some of the extra parens):

++x < y ? ++x : y

which will increment x twice if the condition ++x < y is true.
There's all kinds of nasty side effects possible with the old
version, including having x > y at the end of the statement, which
definitely violates the semantics of min().

The new version avoids these side effects by only evaluating
the given arguments once (assigning them to temp variables,
which will be optimized away in almost all cases anyway), but
in order to do that, the macro needs to know the variable type,
hence the additional argument. In C++, this can be done using
typename or templates, but the kernel's not written in C++
for a number of very good reasons.

Bottom line, I think the new version of min() and friends is
here to stay and is definitely a positive move. One of the down
sides to that is that a lot of people have a lot of cleaning
up to do.


On 08/23/2001 12:03 -0700, J. Imlay wrote:
>> IN getting the AFS kernel modules to compile under linux I dicovered that
>> the were useing the standard min(x,y) macro that whould evaluate which one
>> is smaller. However sometime between 2.4.6 and 2.4.9 a new macro was added
>> to linux/kernel.h
>> this one:
>> #define min(type,x,y) \
>> ({ type __x = (x), __y = (y); __x < __y ? __x: __y; })
>> the old one is
>> #define min(x,y) ( (x)<(y)?(x):(y) )
>> has been around a lot longer and is in lots of header files.
>> The problem here with AFS is that it needs the old definition but the old
>> definition is being over written by the new one... you guys should know
>> all this. But I am just saying that I really think the new macro
>> min(type,x,y) should get a new name. like type_min or something.
>> Thanks,
>> Josie Imlay
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to
>> More majordomo info at
>> Please read the FAQ at
End of included message

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2005-03-22 13:17    [W:0.118 / U:0.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site