Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!vsi!friedl
From: friedl@vsi.COM (Stephen J. Friedl)
Newsgroups: comp.unix.wizards
Subject: Re: too many enumerated types?
Summary: perror(3) is SVID Level 2...
Keywords: SystemV ld perror
Message-ID: <1049@vsi.COM>
Date: 12 Feb 89 07:27:40 GMT
References: <435@laic.UUCP> <955@auspex.UUCP> <9218@bloom-beacon.MIT.EDU>
Distribution: usa
Organization: V-Systems, Inc. -- Santa Ana, CA
Lines: 27

In article <9218@bloom-beacon.MIT.EDU>, scs@adam.pika.mit.edu (Steve Summit) writes:
> 
> This example shows that the ld in question has violated one of
> the cardinal rules* of error messages, and also nicely
> illustrates the importance of these rules.
> [ * good rules deleted, also mentioning perror(3) ]

     For you portability fanatics, perror(BA_LIB) is Level 2 in
the System V Interface Definition (aka the SVID).  `Level 2'
means that the feature is not guaranteed to be supported in the
SVID beyond three years of the Level 2 date, and in this case,
the date is 1/1/1985.

     Reliable sources tell that perror(3) will still be in the
next SVID, but there are `Future Directions' that are much more
substantial (they will make the error messages look more like
VMS).

     What does POSIX say about perror(3)?

     Steve

-- 
Stephen J. Friedl        3B2-kind-of-guy            friedl@vsi.com
V-Systems, Inc.       I speak for you only      attmail!vsi!friedl
Santa Ana, CA  USA       +1 714 545 6442    {backbones}!vsi!friedl
--------Barbara Bush on... on... No, I just can't do it...--------