From: Ray Lee <ray-lk@madrabbit.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: hps@intermeta.de, schwab@suse.de,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: sscanf("-1", "%d", &i) fails, returns 0
Date: 14 Nov 2002 09:34:14 -0800 [thread overview]
Message-ID: <1037295254.27832.11.camel@orca.madrabbit.org> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211122241490.29595-100000@dragon.pdx.osdl.net>
(Sorry for taking so long to review something so short, btw.)
On Tue, 2002-11-12 at 23:06, Randy.Dunlap wrote:
> On 11 Nov 2002, Ray Lee wrote:
> | Explicitly, in the scan conversion you'd do a:
> | unsigned int *u = (unsigned int *) va_arg(args,long long *);
> | *u = (unsigned int) converted_value;
(Luckily you didn't follow my code snippet too closely. Oops.)
> See if this is close...
<snip>
> I think that this patch (to 2.5.47) gets the kernel close
> to the same semantics as C's sscanf() function, which is
> usually a good thing. What say you?
The sample conversions and patch look correct. Time to forward it
onward, me thinks.
Ray
next prev parent reply other threads:[~2002-11-14 17:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 14:54 [PATCH] Re: sscanf("-1", "%d", &i) fails, returns 0 Ray Lee
2002-11-11 19:09 ` Randy.Dunlap
2002-11-11 20:08 ` Andreas Schwab
2002-11-11 20:25 ` Ray Lee
2002-11-13 7:06 ` Randy.Dunlap
2002-11-14 17:34 ` Ray Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 13:32 Douglas Gilbert
2002-11-08 19:22 ` [PATCH] " Randy.Dunlap
2002-11-08 19:41 ` Richard B. Johnson
2002-11-08 19:59 ` Randy.Dunlap
2002-11-08 20:19 ` Linus Torvalds
2002-11-08 22:09 ` Randy.Dunlap
2002-11-10 13:41 ` Henning P. Schmiedehausen
2002-11-11 3:05 ` Randy.Dunlap
2002-11-11 4:19 ` Randy.Dunlap
2002-11-11 9:27 ` Henning Schmiedehausen
2002-11-11 14:38 ` Andreas Schwab
2002-11-08 20:23 ` Richard B. Johnson
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=1037295254.27832.11.camel@orca.madrabbit.org \
--to=ray-lk@madrabbit.org \
--cc=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=schwab@suse.de \
/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