Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ut-sally.UUCP Path: utzoo!decvax!genrad!panda!talcott!harvard!seismo!ut-sally!jsq From: jsq@ut-sally.UUCP (John Quarterman) Newsgroups: mod.std.unix Subject: Re: standardized error messages Message-ID: <2461@ut-sally.UUCP> Date: Wed, 24-Jul-85 12:15:55 EDT Article-I.D.: ut-sally.2461 Posted: Wed Jul 24 12:15:55 1985 Date-Received: Thu, 25-Jul-85 17:42:22 EDT References: <2391@ut-sally.UUCP> Reply-To: std-unix@ut-sally.UUCP Organization: U. Texas CS Dept., Austin, Texas Lines: 36 Approved: jsq@ut-sally.UUCP From: John Quarterman (moderator) Topic: Re: standardized error messages ---------------------------------------------------------------------- From: oliveb!jerry@fortune.uucp (Jerry Aguirre) Date: Mon, 22 Jul 85 21:42:10 pdt Subject: Re: standardized error messages References: <2391@ut-sally.UUCP> > From: Mike Trachtman > Is any thought being given to having the compilers, grep, etc. > give error messages in a standard form, so > that programs will be able to parse them. The sys V announcment that I attended included discussion not only of getopt but of an error library routine. I don't have the syntax handy but it included the severity of the error (warning vs. error vs. fatal), a user supplied message, and optionally the errno determined system error message. I have seen several postings of source which use a similar routine. Does anyone at ATT care to comment on whether an error routine will be included and what the syntax is? Jerry Aguirre @ Olivetti ATC {hplabs|fortune|idi|ihnp4|tolerant|allegra|tymix}!oliveb!jerry ------------------------------ Discussions-Of: UNIX standards, particularly the IEEE P1003 draft standard. Submissions-To: ut-sally!std-unix or std-unix@ut-sally.ARPA Comments-To: ut-sally!std-unix-request or std-unix-request@ut-sally.ARPA UUCP-Routes: {ihnp4,seismo,harvard,gatech}!ut-sally!std-unix Archives-In: ~ftp/pub/mod.std.unix on ut-sally.ARPA (soon sally.UTEXAS.EDU)