Messages in this thread | | | From | "Magnus Naeslund(f)" <> | Subject | Re: macro conflict | Date | Fri, 24 Aug 2001 01:37:38 +0200 |
| |
From: "Andrew Cannon" <ajc@gmx.net> > > What about this then: > > #define min(x,y) ({typeof(x) __x=(x); typeof(y) __y=(y); (__x < __y) ? > __x : __y}) > > This is guaranteed to work the same as the old min/max in all cases but > without side effects. You can still force the comparison to be done with > a certain type by casting the arguments first: > [snip]
Well it's closer but not really what i want. The min/max_type is maybe the way to go, but the above can still bit you if the types differ. Consider max().
char lut[256]; int c1 = 256+rand()%256; char c2 = rand()%256; char dest = lut[max(c2,c1)];
Won't c1 still be returned untruncated?
Ofcourse one will use another construct for these kinds of checks, but maybe your brain collapses just for a second and think that this will return a char.
OK ok bad example, but maybe you see that i have a point here somewhere (under my chair? :) ).
Magnus
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Programmer/Networker [|] Magnus Naeslund PGP Key: http://www.genline.nu/mag_pgp.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |