This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Tue 18 Mar 2014 15:36:18 Roland McGrath wrote: > The context of predefines usually means that the base thing we're looking > at provided by the compiler has to be tested with #ifdef. (For any future > predefines, we should work with compiler folks to suggest that new things > follow the #if-friendly pattern of macros always defined to either 0 or 1 > rather than the typo-prone pattern of sometimes-defined macros.) i like the sentiment, but i'm not sure about the practicality. how do you go about deciding whether a macro should always be defined ? the set of all possible defines gcc might create depending on configuration/target settings ? seems like you'd easily generate a crap ton of noisy defines and blow past the point of usefulness ... -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |