From: Eric Sandeen <sandeen@redhat.com>
To: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/4] Btrfs-progs: new helper to parse string to u64 for btrfs
Date: Thu, 20 Feb 2014 10:43:44 -0600 [thread overview]
Message-ID: <530630C0.20208@redhat.com> (raw)
In-Reply-To: <53055DA5.6080604@cn.fujitsu.com>
On 2/19/14, 7:43 PM, Wang Shilong wrote:
> On 02/20/2014 09:39 AM, Eric Sandeen wrote:
>> On 2/19/14, 7:30 PM, Wang Shilong wrote:
...
>>> + /*
>>> + * if we pass a negative number to strtoull,
>>> + * it will return an unexpected number to us,
>>> + * so let's do the check ourselves firstly.
>>> + */
>>> + if (str[0] == '-') {
>>> + fprintf(stderr, "ERROR: %s may be negative value.\n", str);
>> well, it _is_ a negative value right? (vs. "may be")
>>
>> So perhaps:
>>
>> fprintf(stderr, "ERROR: %s: negative value is invalid.\n", str);
> I use "may be" because the following case:
>
> -123xxxx, -abcd..... something like these, these string are invalid,
> but they are not negative number...So i have not thought a better idea
> to tell user what is wrong with input.:-)
Ok; well, sorry for being nitpicky. :) But user error messages probably
should be very clear and unambiguous; we may as well do this right.
So what about this:
Do strtoull first, and *if* it passes numeric parsing, but str[0] == '-',
*then* say "ERROR: %s: negative value is invalid."
-Eric
next prev parent reply other threads:[~2014-02-20 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 1:30 [PATCH v2 0/4] Btrfs-progs: cleanups: new helper for parsing string to u64 Wang Shilong
2014-02-20 1:30 ` [PATCH v2 1/4] Btrfs-progs: new helper to parse string to u64 for btrfs Wang Shilong
2014-02-20 1:39 ` Eric Sandeen
2014-02-20 1:43 ` Wang Shilong
2014-02-20 16:43 ` Eric Sandeen [this message]
2014-02-20 1:30 ` [PATCH v2 2/4] Btrfs-progs: switch to arg_strtou64() part1 Wang Shilong
2014-02-20 1:30 ` [PATCH v2 3/4] Btrfs-progs: switch to arg_strtou64() part2 Wang Shilong
2014-02-20 1:30 ` [PATCH v2 4/4] Btrfs-progs: switch to arg_strtou64() part3 Wang Shilong
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=530630C0.20208@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangsl.fnst@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.