>Date: Mon, 09 Jun 2008 12:47:38 -0400 >From: Dan McDonald <danmcd at sun.com> > ... ... ... > >> Are there any #define's to conditionally enable or disable these being >> added to the namespace? (I'm thinking along the lines of dialect options >> that the C compiler exports, e.g. __STDC__, _POSIX_C_SOURCE, and >> __EXTENSIONS__.) > >That's why I went to Don Cragun first. > >Three of the five documented were ALREADY IN sys/time.h. The two new ones >(timeradd/timersub) are in the same blocked areas as the first three.
Just like other non-standard functions and macros in standard headers, these macros are invisible in standards conforming compiles unless the application asks for a polluted namespace by #defining __EXTENSIONS__ before including <sys/time.h>. > >> The other question (and this is just general, not architectural in nature) >> is, given that these functions seem to be widely useful and popular, are >> you aware of any movement in any of the standards bodies (POSIX) to >> standardize on these? > >Ask Don -- that's his department. No requests to include any of these macros have been sent to the TOG Base Working Group, IEEE PASC, ISO/IEC/JTC1/SC22/WG15, or The Austin Group e-mail aliases nor through the interpretations processes at any of these four organizations. - Don > >Dan
