Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!romp!auschs!awdprime!testsys.austin.ibm.com!mbrown From: mbrown@testsys.austin.ibm.com (Mark Brown) Newsgroups: comp.unix.aix Subject: Re: Error messages Message-ID: <6093@awdprime.UUCP> Date: 25 Mar 91 00:58:41 GMT References: <1991Mar11.085414.2650@ccu1.aukuni.ac.nz> Sender: news@awdprime.UUCP Reply-To: mbrown@testsys.austin.ibm.com (Mark Brown) Organization: IBM Austin, TX Lines: 23 kstailey@wookumz.gnu.ai.mit.edu (Kenneth Stailey) writes: |graeme@ccu1.aukuni.ac.nz (Graeme Moffat) writes: | 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. If one were to read IEEE POSIX 1003.2 Draft 11 Sec. 2.11.6.1 and 2.11.6.2, one would see that this assertion is baseless. I respectfully suggest that one *read* the draft standard, and avoid speculation (although getting copies *is* expensive and difficult for the average person)? Mark Brown IBM PSP Austin, TX. (512) 823-3741 VNET: MBROWN@AUSVMQ MAIL: mbrown@testsys.austin.ibm.com OR uunet!testsys.austin.ibm.com!mbrown The nice thing about standards is that there are so many to choose from! DISCLAIMER: Any personal opinions stated here are just that.