Path: utzoo!utgpu!watmath!clyde!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.lang.c
Subject: Re: retiring gets(3)
Message-ID: <6927@chinet.chi.il.us>
Date: 11 Nov 88 04:05:18 GMT
References: <1988Nov8.054845.23998@utstat.uucp> <8841@smoke.BRL.MIL>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Public Access Unix
Lines: 11

In article <8841@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
>By the way, have you removed scanf() from your C library as well?  Or
>sprintf()?  Or strcpy()?  They can be misused in the same way as gets().
>Let us know how happy your customers are once ALL such routines are gone.

With gets() and strcpy() a safe alternative exists.  Is everyone really
going to write their own safe versions of scanf() and sprintf()?  I always
wondered why the standard library versions have no way to control the
size of the output - maybe real programers like core dumps?

Les Mikesell