Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!cuae2!killer!molly
From: molly@killer.UUCP
Newsgroups: comp.lang.c
Subject: A better perror() (Was: Re: Accessing argc ...)
Message-ID: <1351@killer.UUCP>
Date: Tue, 18-Aug-87 01:07:31 EDT
Article-I.D.: killer.1351
Posted: Tue Aug 18 01:07:31 1987
Date-Received: Thu, 20-Aug-87 01:38:04 EDT
References: <22@flmis06.ATT.COM> <28700015@ccvaxa> <853@mcgill-vision.UUCP>
Organization: The Unix(tm) Connection, Dallas, Texas
Lines: 28
Summary: What about munging a PD printf?

In article <853@mcgill-vision.UUCP>, mouse@mcgill-vision.UUCP (der Mouse) writes:
> In article <28700015@ccvaxa>, aglew@ccvaxa.UUCP quotes:
> > I have always thought that perror(str) was silly - sometimes I want
> > str to be the command name, sometimes the command plus all
> > arguments...
> 
> [ ... ] Wish perror() were printflike, perhaps like
> syslog() - syslog() accepts a printf format, except that %m means
> insert sys_errlst[errno].

I have seen a few public domain printf's come down the line (the most
recent even had a %R option for Roman Numerals - just what I need
next time a write a clock program ...

The varargs functions and whatnot look more than adaquate for doing
something like this.  What exactly is `syslog()', and how would I get
ahold of it?

If there ain't a PD syslog, I might be convinced to convert a printf()
into one if someone mails the man-page ... it might just get done in
time for Christmas.

Molly
-- 
       Molly Fredericks       UUCP: { any place real }!ihnp4!killer!molly
    Disclaimer:  Neither me, nor my cat, had anything to do with any of this
  "I love giving my cat a bath, except for all those hairs I get on my tongue"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~