From: Igor Mammedov <imammedo@redhat.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [ [PATCH 1/2] cutils:change strtosz_suffix_unit function
Date: Wed, 12 Dec 2012 11:12:03 +0100 [thread overview]
Message-ID: <20121212111203.2cef65d9@nial.usersys.redhat.com> (raw)
In-Reply-To: <1354852190-15095-1-git-send-email-lig.fnst@cn.fujitsu.com>
On Fri, 7 Dec 2012 11:49:49 +0800
liguang <lig.fnst@cn.fujitsu.com> wrote:
> if value to be translated is larger than INT64_MAX,
> this function will not be convenient for caller to
> be aware of it, so change a little for this.
>
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
> cutils.c | 5 +++--
> 1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/cutils.c b/cutils.c
> index 4f0692f..8905b5e 100644
> --- a/cutils.c
> +++ b/cutils.c
> @@ -219,11 +219,11 @@ static int64_t suffix_mul(char suffix, int64_t unit)
> int64_t strtosz_suffix_unit(const char *nptr, char **end,
> const char default_suffix, int64_t unit)
> {
> - int64_t retval = -1;
> + int64_t retval = -1, mul;
> char *endptr;
> unsigned char c;
> int mul_required = 0;
> - double val, mul, integral, fraction;
> + double val, integral, fraction;
>
> errno = 0;
> val = strtod(nptr, &endptr);
> @@ -246,6 +246,7 @@ int64_t strtosz_suffix_unit(const char *nptr, char
> **end, goto fail;
> }
> if ((val * mul >= INT64_MAX) || val < 0) {
> + retval = 0;
Why not to add Error argument to return errors instead of using return value?
That way function would be easier to generalize in future to handle whole
INT64 range. And callers would check only returned error instead of return
value or if 'end' == 0.
> goto fail;
> }
> retval = val * mul;
next prev parent reply other threads:[~2012-12-12 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 3:49 [Qemu-devel] [ [PATCH 1/2] cutils:change strtosz_suffix_unit function liguang
2012-12-07 3:49 ` [Qemu-devel] [ [PATCH 2/2] qemu-img:report size overflow error message liguang
2012-12-11 15:11 ` Markus Armbruster
2012-12-12 0:59 ` li guang
2012-12-11 9:52 ` [Qemu-devel] [ [PATCH 1/2] cutils:change strtosz_suffix_unit function Stefan Hajnoczi
2012-12-11 15:06 ` Markus Armbruster
2012-12-12 0:58 ` li guang
2012-12-12 8:18 ` Stefan Hajnoczi
2012-12-12 10:12 ` Igor Mammedov [this message]
2012-12-13 8:03 ` Markus Armbruster
2012-12-13 9:11 ` Igor Mammedov
2012-12-13 12:09 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2012-12-14 4:08 [Qemu-devel] " liguang
2012-12-14 12:09 ` Markus Armbruster
2012-12-14 13:45 ` Igor Mammedov
2012-12-17 1:09 ` li guang
2012-12-17 0:35 ` li guang
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=20121212111203.2cef65d9@nial.usersys.redhat.com \
--to=imammedo@redhat.com \
--cc=kwolf@redhat.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 NNTP newsgroup(s).