Newsgroups: comp.sources.d
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Subject: Re: v01INF1: Status - Status of comp.sources.reviewed
Message-ID: <FUSA56C@xds13.ferranti.com>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
References: <1991Apr14.232818.15851@athena.mit.edu> <12409:Apr1513:14:4 <1991Apr16.131650.24389@scuzzy.in-berlin.de> <1307:Apr1702:20:0991@kramden.acf.nyu.edu>
Date: Wed, 17 Apr 91 21:36:37 GMT

In article <1307:Apr1702:20:0991@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> but I didn't want to sacrifice portability just to get UNIX error
> messages. I welcome suggestions for how to solve this.

How does calling "perror" sacrifice portability? Any compiler that doesn't
include a functioning perror() in their standard I/O library isn't worth
supporting... it's probably got other major limitations even if it satisfies
the letter of the ANSI C standard.
-- 
Peter da Silva.  `-_-'  peter@ferranti.com
+1 713 274 5180.  'U`  "Have you hugged your wolf today?"
