public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mtk.manpages at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug manual/16776] Endless loop in strtol example
Date: Wed, 30 Apr 2014 03:55:00 -0000 [thread overview]
Message-ID: <bug-16776-131-bByRCLXWYT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16776-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16776
--- Comment #3 from Michael Kerrisk <mtk.manpages at gmail dot com> ---
(In reply to Olaf van der Spek from comment #2)
> Bugs in examples are bad, they *will* be copied into real code.
I'mquite agree.
But, Olaf, why not just provide a patch? Seems to me the solution is just an
API of the form:
int sum_ints_from_string(char * str, int &result)
which returns 0 on failure, 1 on success.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-30 3:55 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 ` [Bug manual/16776] " neleai at seznam dot cz
2014-04-28 18:46 ` olafvdspek at gmail dot com
2014-04-30 3:55 ` mtk.manpages at gmail dot com [this message]
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-bByRCLXWYT@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).