From: Shriramana Sharma <samjnaa@gmail.com>
To: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: A safe scanf function
Date: Tue, 28 Feb 2006 09:59:21 +0530 [thread overview]
Message-ID: <200602280959.21099.samjnaa@gmail.com> (raw)
In-Reply-To: <17411.7908.386568.805492@cerise.gclements.plus.com>
Monday, 27 February 2006 21:16 samaye tvayaa likhitam:
> And scanf() isn't "unsafe"; it just doesn't do what you want in your
> particular application. There are plenty of situations where scanf()
> does the right thing and getline() + sscanf() doesn't; e.g.:
OK, so scanf does have its own applications.
I would like to place on record that I used fgets and sscanf and the problem I
was experiencing was totally removed.
--
Tux #395953 resides at http://samvit.org
playing with KDE 3.51 on SUSE Linux 10.0
$ date [] CCE +2006-02-28 W09-2 UTC+0530
prev parent reply other threads:[~2006-02-28 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 8:17 A safe scanf function Shriramana Sharma
2006-02-26 15:34 ` Glynn Clements
2006-02-27 15:15 ` Shriramana Sharma
2006-02-27 15:46 ` Glynn Clements
2006-02-28 4:29 ` Shriramana Sharma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602280959.21099.samjnaa@gmail.com \
--to=samjnaa@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).