public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/16776] Endless loop in strtol example
Date: Mon, 28 Apr 2014 16:37:00 -0000	[thread overview]
Message-ID: <bug-16776-131-b4Dgs5pcAW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16776-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16776

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |neleai at seznam dot cz
         Resolution|---                         |INVALID

--- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> ---
It is just example, clarity there is preferred.

It does not handle input validation, you need to supply valid input. For user
input you should use scanf anyway to handle thousand separators and such.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2014-04-28 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-29 16:01 [Bug manual/16776] New: " olafvdspek at gmail dot com
2014-04-28 16:37 ` neleai at seznam dot cz [this message]
2014-04-28 18:46 ` [Bug manual/16776] " olafvdspek at gmail dot com
2014-04-30  3:55 ` mtk.manpages at gmail dot com
2014-04-30  7:16 ` olafvdspek at gmail dot com
2014-04-30  7:28 ` mtk.manpages at gmail dot com
2014-06-12 19:51 ` fweimer at redhat dot com
2014-06-13  9:16 ` fweimer at redhat dot com

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=bug-16776-131-b4Dgs5pcAW@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).