From: Petter Reinholdtsen <pere@hungry.com>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Tiny libc fixes
Date: Tue, 20 Apr 2004 15:36:00 -0000 [thread overview]
Message-ID: <20040420153558.GA11499@saruman.uio.no> (raw)
In-Reply-To: <20040420131028.GA5191@sunsite.ms.mff.cuni.cz>
[Jakub Jelinek]
> 1) Reverting the %% whitespace change from yesterday.
> Some OSes don't eat the whitespace there while others do, the ISO
> C99 standard only lists %c, %[ and %n as not eating whitespace,
> so it is probably better to stay with previous glibc behaviour
> here.
I agree that it is probably a good idea to stay conservative, but
believe it is a good idea to ask for the C standard to be made clearer
on this point.
Do you have information on how the various implementations of sscanf()
behave in this respect?
The Open Group Base Specification seem clearer on the issue
<URL:http://www.opengroup.org/onlinepubs/007904975/functions/sscanf.html>:
Input white-space characters (as specified by isspace() ) shall be
skipped, unless the conversion specification includes a [ , c , C ,
or n conversion specifier.
next prev parent reply other threads:[~2004-04-20 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 15:22 Jakub Jelinek
2004-04-20 15:36 ` Petter Reinholdtsen [this message]
2004-04-20 18:54 ` Ulrich Drepper
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=20040420153558.GA11499@saruman.uio.no \
--to=pere@hungry.com \
--cc=libc-hacker@sources.redhat.com \
/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).