*BSD News Article 18866


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!darwin.sura.net!news.dfn.de!Germany.EU.net!mcsun!sun4nl!hacktic!not-for-mail
From: cor@hacktic.nl (Cor)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Using gets() [ Was Re: nn ]
Date: 25 Jul 1993 16:55:36 +0200
Organization: Hack-Tic, networking for the masses
Lines: 21
Message-ID: <22u6tmINN2t6@xs4all.hacktic.nl>
References: <OLEG.93Jul17185604@gd.cs.CSUFresno.EDU> <1993Jul19.005949.28286@oucsace.cs.ohiou.edu> <CAKu2r.10rt@austin.ibm.com> <CAq222.8E4@sugar.NeoSoft.COM>
NNTP-Posting-Host: xs4all.hacktic.nl

peter@NeoSoft.com (Peter da Silva) writes:

>In article <CAKu2r.10rt@austin.ibm.com> boyd@pal411.austin.ibm.com writes:
>> I will not debate whether the function is a good one or not.  However,
>> since it is included for the sake of compatibility, I would argue that
>> it should be distributed in a fashion that allows its use.

>I agree. gets should work as documented, but it should probably be stuck
>in an "obsolete" library, to be linked in as "-lobso" for programs that
>use broken functions. Stick strtok in there as well :>.

Phew, at least *some* people that agree with my original posting.
My whole argument was that I didnt like gets() putting anything on stderr,
cause it causes things to fail (like in this example, nn)
We all know gets() isnt safe, that wasnt the issue. 
cor
-- 
| cor@hacktic.nl | Hack-Tic System Management | +31-20-6001480-3 (VMB)  |
| -------------------------------------------------------------------------|
|   ######### Signature Virus Running. Contamination Complete #########    |
+--------------------------------------------------------------------------+