Xref: utzoo comp.bugs.4bsd:1712 comp.std.c:4233 comp.lang.c:35745
Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!cs.utexas.edu!bcm!convex!usenet
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.bugs.4bsd,comp.std.c,comp.lang.c
Subject: Re: Safe coding practices (was Re: Bug in users command)
Message-ID: <1991Feb03.181937.9090@convex.com>
Date: 3 Feb 91 18:19:37 GMT
References: <1991Jan29.203900.11987@Think.COM> <9k9G!#9a@cs.psu.edu> <27A6EBDB.2F16@tct.uucp>
Sender: usenet@convex.com (news access account)
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
Lines: 26
Nntp-Posting-Host: pixel.convex.com

From the keyboard of chip@tct.uucp (Chip Salzenberg):
: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.

It's not the world, but it's a start.  Do you have a scheme for fixing
everything everywhere simultaneously?  It's a hard problem.  (I often wish
RTM's Internet worm had gone around fixing broken code: the ultimate
update engine. :-)

: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.

Ug.  If it's written once, published, and made available for use free
of charge *and* without viral strings attached, each site or programmer
won't have to re-invent the wheel.  Of course, sites without source are
still largely at the mercy of vendors.

--tom
--
Still waiting to read alt.fan.dan-bernstein using DBWM, Dan's own AI
window manager, which argues with you 10 weeks before resizing your window.
    Tom Christiansen	tchrist@convex.com	convex!tchrist