Newsgroups: comp.unix.aix Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!mintaka.lcs.mit.edu!kstailey From: kstailey@wookumz.gnu.ai.mit.edu (Kenneth Stailey) Subject: Re: Error messages In-Reply-To: graeme@ccu1.aukuni.ac.nz's message of 11 Mar 91 08:54:14 GMT Message-ID: Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius) Organization: /home/fsg/kstailey/.organization References: <1991Mar11.085414.2650@ccu1.aukuni.ac.nz> Date: 24 Mar 91 10:22:07 Lines: 28 In article <1991Mar11.085414.2650@ccu1.aukuni.ac.nz> graeme@ccu1.aukuni.ac.nz (Graeme Moffat) writes: Path: mintaka!olivea!uunet!comp.vuw.ac.nz!waikato.ac.nz!aukuni.ac.nz!graeme From: graeme@ccu1.aukuni.ac.nz (Graeme Moffat) Newsgroups: comp.unix.aix Date: 11 Mar 91 08:54:14 GMT Organization: University of Auckland, New Zealand. Lines: 18 The rs6000 error messages are preceded by fancy looking 7 digit numbers... Gee, doesn't POSIX 1003.2 require that most error messages are precisely specified in terms of the printf string that must be used to produce them. The idea is that programs can grep for error strings, so they must be exact. This means that close to 100% of the error strings must be changed. I can't wait to see what happens when the government bids can't be won without this because "designed to be POSIX compliant" isn't good enough. ("designed to be" is IBMspeak for "isn't") -- @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@ Disclaimer: This message is sold by weight not volume; | contents may have settled during shipment. @ @ replys to kstailey@gnu.ai.mit.edu or kstailey@leidecker.gsfc.nasa.gov | NBCS: B4 f m w- c(+) p+ k+ s+ why jack off when you can jack in? @-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@-@