News for hackers. Stuff that matters.
Re:The Little C Function From Hell by cperciva on Thursday June 21, 2012 @10:15AM (#4142050)
Your "char" in a preprocessor directive is either a uintmax_t or an intmax_t. Either way, it's going to end up as #if 128 > 127 or #if 256 > 255 -- so the first case will always end up being included.
Re:The Little C Function From Hell by krollew on Friday June 22, 2012 @02:29AM (#4145719)
It's standard behaviour or one compiler does so? Outside preprocessor char has another meaning? Thanks anyway.
Re:The Little C Function From Hell by cperciva on Friday June 22, 2012 @03:27AM (#4145832)
Outside of the preprocessor, the char type is a one-byte integer (whether it's signed or not is implementation-defined).
Re:The Little C Function From Hell by krollew on Friday June 22, 2012 @04:44AM (#4145995)
So the good solution is make a test that finds it out, for example in configuration script and set proper preprocessor constant and test that constant instead.