Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!teknowledge-vaxc!sri-unix!quintus!ok
From: ok@quintus.UUCP (Richard A. O'Keefe)
Newsgroups: comp.lang.c
Subject: Re: A tale of two C's.
Message-ID: <930@cresswell.quintus.UUCP>
Date: 5 May 88 07:44:19 GMT
References: <152@ghostwheel.UUCP> <7691@brl-smoke.ARPA> <154@ghostwheel.UUCP> <7821@brl-smoke.ARPA>
Organization: Quintus Computer Systems, Mountain View, CA
Lines: 13

In article <7821@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
: In article <924@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes:
: >It's worth noting that exactly this technique is an offical part of the
: >System V library interface (see 'matherr').
: 
: matherr() was intended to be replaced by user code (and so documented)
: as a deliberate aspect of its design.  None of the other library routines
: is obliged to support such perversion.

Yes, I know that.  I guess it's a mistake to try to be too succinct in news.
matherr() is a compellingly good(bad) example of how _not_ to design an
error-handling interface.  I thought I should provide some argument against
replacing library routines as well as some for.