On Feb 8, 2008 10:15 AM, <Casper.Dik at sun.com> wrote: > > > >printf also has to ingore -- so that an old script that does > > printf -- > >will no longer generate output. > > That part Solaris printf does properly.
Roland commented that: "Erm... what should we do in this case ? The upcoming changes for /usr/bin/printf in OS/Net will trigger the same error in those scripts (remember it's stabilty status "Standard" since /usr/bin/printf _must_ pass the VSW&co. test suites)." I'm a little lost here on how Sun typically handles cases like these. What happens when a bug-fix causes unexpected behaviour in programs and they are not exactly doing something *intentionally* wrong? In this case, it looks like ksh93 won't cause any more problems than the upcoming changes. With that in mind, it seem as though this could be considered a non-issue? -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "To err is human -- and to blame it on a computer is even more so." - Robert Orben
