[ On Saturday, June 8, 2002 at 13:41:45 (-0400), Mason Loring Bliss wrote: ]
> Subject: Re: This should be the final cat(1) patch...
>
> I'm researching this right now, trying to understand where and how err(3)
> and warn(3) are actually defined on a system with no err.h... Given that
> part of this exercise is to produce a new host tool for inclusion in
> TOOLDIR, using non-standard function calls seems uncool. (This is, for
> instance, why I'm using fcntl(2) instead of the much simpler flock(2).)

They're not.  err(3) et al are *BSD-isms (very recent, at that) and are
not portable.  Don't use them in code that's intended to be portable.

-- 
								Greg A. Woods

+1 416 218-0098;  <gwoods@acm.org>;  <g.a.woods@ieee.org>;  <woods@robohack.ca>
Planix, Inc. <woods@planix.com>; VE3TCP; Secrets of the Weird <woods@weird.com>