Glenn Fowler wrote: > > on solaris (and/or in general) can a user call vanilla cc with > cc -D_ISOC99_SOURCE > and expect it to work, or can such usage require some implementation > semantic knowledge, like extra -D or -l options
I don't know... I've been trying find any documentation in Solaris but it seems the only places where |_ISOC99_SOURCE| is used in Solaris is... -- snip -- $ ggrep -r _ISOC99_SOURCE /usr/man $ ggrep -r _ISOC99_SOURCE /usr/include 2>/dev/null /usr/include/gstreamer-0.10/gst/floatcast/floatcast.h: #define _ISOC99_SOURCE 1 $ ggrep -r _ISOC99_SOURCE /opt/SUNWspro/ 2>/dev/null $ ggrep -r _ISOC99_SOURCE /usr/sfw/ 2>/dev/null -- snip -- ... which leads to the question what |_ISOC99_SOURCE| should do... > in a similar vein, can there be a difference between > cc -D_ISOC99_SOURCE > and > #define _ISOC99_SOURCE 1 > before and #include's > e.g., can a cc inplementation overload -D_ISOC99_SOURCE to enable > other appropriate options and libs? > > practical (system x does it) and standard-ese responses welcome Don/Chris... can you help, please ? ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
