cc: roland.mainz at nrubsig.org Subject: Re: Re: [ksh93-integration-discuss] printf syntax and /sbin/shcompatibility --------
> AFAIK it's a "bug" and not an "incompatibity". The Marvell package > script described in http://defect.opensolaris.org/bz/show_bug.cgi?id=502 > just hits the unfortunate case where 1) an utilty in Solaris does not > implement the POSIX standard correctly and 2) something external (the > Marvell package script) relies on this behaviour. > AFAIK there are two options in this case: > 1) Treat the issue as bug in /usr/bin/printf and report problem in the > Marvell script to the vendor > 2) Treat the issue as a compability issue. In this case we have to > change the stabilty status of /usr/bin/printf from "Standard" to > "Commited", create /usr/xpg6/bin/printf (as location for the version of > "printf" which fully conforms to the standards) and bind the ksh93 > builtin to /usr/xpg6/bin/printf (as a side-effect we wouldn't be able to > implement all the C99 features in /usr/bin/printf since this would > change a commited interface) > Another recommendation is to modify the option parser so that an argument begining with --- is treated as an option argument. The standards doesn't define the behavior in this case and the AST tool kit only handles options that begin with - or -- so that it won't affect AST tools. The Marvel script uses has an argument beginning with --- so it will run ok with this change. David Korn dgk at research.att.com
