Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!mcnc!ecsvax!dukeac!bet
From: bet@dukeac.UUCP (Bennett Todd)
Newsgroups: comp.sources.d
Subject: Re: PAX : Too many open files
Message-ID: <1244@dukeac.UUCP>
Date: 20 Feb 89 16:03:56 GMT
References: <2895@mhres.mh.nl>
Reply-To: bet@dukeac.UUCP (Bennett Todd)
Organization: Radiology, Duke Med. Center, Durham, NC
Lines: 11

I wanted to check all system calls no matter what, and yet not have to deal
with the clutter of error-checking in the (common) case where all I'm going to
do is give an error message and exit on failure. So I wrote libbent. Now, if I
don't want to deal with the possibility of failure explicitly in my code, I
just prepend 'e' to the routine I am about to call, and link with -lbent. I
recently posted libbent to comp.lang.c. Maybe, if I continue to get
encouraging feedback, I will post some subsequent version to
comp.sources.unix. 

-Bennett
bet@orion.mc.duke.edu