On Sun, May 23, 2010 at 10:25 AM, Richard L. Hamilton <rlha...@smart.net> wrote: [snip] > My impression is that a number of the AST tools have picked up the > major options previously unique to the GNU tools, while trying to retain > better standards compliance. Assuming that to be true, I think they'd > be the way to go.
The goal for the AST utilities is to conform _strictly_ to the POSIX/SUS standards (now quickly moving towards SUSv4) and add those BSD and GNU extensions which are 1) usefull and 2) do not conflict with the POSIX/SUS standards (e.g. we won't add BSD/GNU options which will cause the utilities to break the POSIX/SUS test suite or specification [1]). >From an ARC point of view the POSIX/SUS APIs (and options) are "Commited" while the non-standard options remain uncommited unless there are more than one (or better: two) implementations out there which implement it identically and the "upgrade" of the interface stability makes sense. [1]=OK, I am lying a tiny bit... we have support for multiple defaults for the utilities which can be toggled via a "secret" switch. This allows (if needed) that one utilitiy can act as replacement for Solaris, GNU and BSD utilties at the same time with one implementation (this saves code space, too (which is one of the major design considerations behind the project, e.g. to be one of the fastest implementations but one of the smallest, too (without sacrifying conformance))). But the default should _ALWAYS_ be "standard conformance by default". ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.ma...@nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
