Xref: utzoo comp.bugs.4bsd:1700 comp.std.c:4227 comp.lang.c:35672
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!pdn!tscs!tct!chip
From: chip@tct.uucp (Chip Salzenberg)
Newsgroups: comp.bugs.4bsd,comp.std.c,comp.lang.c
Subject: Re: Safe coding practices (was Re: Bug in users command)
Message-ID: <27A6EBDB.2F16@tct.uucp>
Date: 30 Jan 91 15:52:59 GMT
References: <87774@tut.cis.ohio-state.edu> <1991Jan29.203900.11987@Think.COM> <9k9G!#9a@cs.psu.edu>
Organization: Teltronics/TCT, Sarasota, FL
Lines: 13

According to schwartz@groucho.cs.psu.edu (Scott Schwartz):
>Happily, Chris Torek's new 4.4BSD stdio provides a way to
>read lines of any length using ``fgetline''.

BSD isn't the world; fixing 4.4BSD won't help me.

Each site (or programmer) needs to write fgetline() or its moral
equivalent using getc(), malloc() and realloc(), and use it every time
gets() or fgets() would have been used.
-- 
Chip Salzenberg at Teltronics/TCT     <chip@tct.uucp>, <uunet!pdn!tct!chip>
 "I want to mention that my opinions whether real or not are MY opinions."
             -- the inevitable William "Billy" Steinmetz