From: Takashi Iwai <tiwai@suse.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] conf.c: parsing floating point numbers
Date: Wed, 03 Jul 2002 11:23:52 +0200 [thread overview]
Message-ID: <s5hofdprwpj.wl@alsa2.suse.de> (raw)
In-Reply-To: <3D2169B3.FA0D9F45@ladisch.de>
At Tue, 02 Jul 2002 10:52:03 +0200,
Clemens Ladisch wrote:
>
> When parse_value finds something looking like a number, it first calls
> safe_strtoll to test whether the value's type is integer.
> Unfortunately, safe_strtoll simply grabs anything which may be an
> integer, and doesn't check for any following characters (e.g. the
> decimal point of a floating point number).
>
> This means that all floating point numbers are parsed as integers.
>
> The patch adds a check for the end of the string, similar to
> safe_strtol and safe_strtod.
thanks, applied to cvs.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-07-03 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 8:52 [PATCH] conf.c: parsing floating point numbers Clemens Ladisch
2002-07-03 9:23 ` Takashi Iwai [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=s5hofdprwpj.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.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