Re: gets() and getchar

Article View: comp.std.c

Article #3803

#3803

From: halasz
Date: Mon, 21 Aug 1995 17:41

8 lines
792 bytes

halasz@caip.rutgers.edu:
: What is wrong with endouing "gets" with a limit?

In article <412n2q$ka4@kruuna.helsinki.fi>, wirzeniu@cc.Helsinki.FI (Lars Wirzenius) writes:
: Then it isn't compatible with the old gets and will break software.  Not good.
: Reusing names for new purposes is not a good idea.

There alreddie are special functions with optional arguments ....

Technical Details

Message-ID: <9508211033.aa04645@kewszeg.UUCP>

Path: arc1-ca.pugleaf.net!cs.utexas.edu!not-for-mail

References: <Pine.ULT.3.91.950807194041.19202A-100000@mars> <412n2q$ka4@kruuna.helsinki.fi>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!cs.utexas.edu!not-for-mail
From: halasz@kewszeg.norden1.com
Newsgroups: comp.std.c
Subject: Re: gets() and getchar
Date: 21 Aug 1995 12:41:17 -0500
Organization: UTexas Mail-to-News Gateway
Sender: nobody@cs.utexas.edu
Message-ID: <9508211033.aa04645@kewszeg.UUCP>
References: <Pine.ULT.3.91.950807194041.19202A-100000@mars> <412n2q$ka4@kruuna.helsinki.fi>
NNTP-Posting-Host: news.cs.utexas.edu

Reply to Parent Message