Andreas Fritiofson wrote: > This would help to avoid picking a magic value for true. > #define false 0 > #define true (!false) // this will actually evaluate to 1 > IMHO, this is unnecessary obfuscation. The C standard guarantees that this will evaluate to 1, so why not write 1 directly?
> On the other hand, code that relies on specific values for true is > IMHO buggy or at least error prone (especially if "true" == -1!!), > which implies that the define shouldn't be used at all in comparisons. > That includes pointless constructs like "if ((a == b) == true) ..." > Full ACK. cu Michael _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
