On Mon, 18 Feb 2008 10:16:28 +0100 Casper.Dik at Sun.COM wrote: > The bug is in the driver's request script, NOT in Solaris printf.
> Both ksh93 printf and Solaris printf are standard comforming; but they > are not compatible in their behaviour in non-standard conforming > invocations. right we (ast) took a hit back when we added self documentation to all of the ast utilities -- there were a few non-conformining user applications to deal with looking back it turned out to be a good move because now all ast utilities can be extended with new options without hitting backwards compatibility another side of the issue is that some future standard may add options to utilities that currently have None, and implementations will have to deal with compatibility on a case by case basis this is what I meant by "most users code to eliminate warnings": the ast change brought a bit of pain, but it was a one time hit (for ast users), and it spanned all of the ast utilities -- by coding to eliminate warnings (e.g., "invalid option"), ast users were nudged into writing standards conforming applications (w.r.t. options vs. operands) that port to any other standard conforming implementation of course extension options are another side of the compatibility issue; ksh builtins help to avoid some of portability the problems there -- Glenn Fowler -- AT&T Research, Florham Park NJ --
