Re: gets() and getchar

Article View: comp.std.c

Article #3811

#3811

From: caip.rutgers.eduhalasz
Date: Mon, 21 Aug 1995 23:13

8 lines
762 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: <41b3ut$s2@caip.rutgers.edu>

Path: arc1-ca.pugleaf.net!caip.rutgers.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!caip.rutgers.edu!not-for-mail
From: caip.rutgers.edu!halasz
Newsgroups: comp.std.c
Subject: Re: gets() and getchar
Date: 21 Aug 1995 19:13:33 -0400
Organization: .
Sender: halasz@caip.rutgers.edu
Message-ID: <41b3ut$s2@caip.rutgers.edu>
References: <Pine.ULT.3.91.950807194041.19202A-100000@mars> <412n2q$ka4@kruuna.helsinki.fi>
NNTP-Posting-Host: caip.rutgers.edu

Reply to Parent Message