This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
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 Fri, Jul 23, 2004 at 01:19:46PM -0700, Ulrich Drepper wrote: > Joseph S. Myers wrote: > > > c99 is the name of the compiler to "accept source code conforming to the > > ISO C standard". For example, > > And once -D_POSIX_C_SOURCE=200112L is defined all this ISO C nonsense > must be completely out of the way. No __STRICT_ANSI__, since non-ISO C > stuff is used. The same applies to a few other defines. Only if none > is defined can this silly strict ISO C business take place. I guess it all depends what exact meaning __STRICT_ANSI__ is supposed to have. Either its definition chooses only ISO C90 (resp. C99) features in the headers, or it can be combined with other feature set macros with the result of a union between ISO C90 (resp. C99) features and features selected by the other feature macros. The __STRICT_ANSI__ documentation in info gcc doesn't seem to favor either of these definitions, at least in my reading. Jakub
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |