Re: Some rambling about strdup()'s standard and other standards issues

[Greg Troxel <gdt%lexort.com@localhost>]

"Greg A. Woods" <woods%planix.ca@localhost> writes:

> Should NetBSD kill off _NETBSD_SOURCE if __STRICT_ANSI__ is defined?  Is
> that really a good hint that the code will also define something like
> _POSIX_SOURCE if it also wants to use POSIX "extensions"?

No, because I see "really comply with the C standard" as being separate
from "hide OS features not required by CNN".   To me the point of
__STRICT_ANSI__ is to throw errors on gnu extensions to C, so that the
code would build with some other compiler.