All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jamie Lokier <jamie@shareable.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] Add test suite for json marshalling
Date: Fri, 13 Nov 2009 08:05:56 -0600	[thread overview]
Message-ID: <4AFD67C4.9070100@codemonkey.ws> (raw)
In-Reply-To: <20091113031431.GF19405@shareable.org>

Jamie Lokier wrote:
> Anthony Liguori wrote:
>   
>> After checking that we can demarshal, marshal again and compared to
>> the expected decoded value.  This doesn't work so well for floats
>> because they cannot be accurately represented in decimal but we try
>> our best.
>>     
>
> Good sprintf/scanf/strtod implementations do guarantee that what's
> printed and then parsed gets back the same floating point value, as
> long as you have printed sufficient decimal digits.
>
> I'm not sure if FLT_DIG/DLB_DIG are the right number of digits,
> though.  Glibc's documentation of those is confusing and they might
> mean something a little different.
>   

Eh, I played around quite a bit and the results were disappointing.

$ printf "%f\n" 43.32
43.320000
$ printf "%0.32f\n" 43.32
43.31999999999999999972244424384371

Regards,

Anthony Liguori
> -- Jamie
>
>
>   

  reply	other threads:[~2009-11-13 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 19:24 [Qemu-devel] [PATCH 1/3] QDict: Introduce qdict_iter() Anthony Liguori
2009-11-11 19:24 ` [Qemu-devel] [PATCH 2/3] Provide marshalling mechanism for json Anthony Liguori
2009-11-11 19:24 ` [Qemu-devel] [PATCH 3/3] Add test suite for json marshalling Anthony Liguori
2009-11-13  3:14   ` Jamie Lokier
2009-11-13 14:05     ` Anthony Liguori [this message]
2009-11-16  2:26       ` Jamie Lokier
2009-11-18 10:48     ` Markus Armbruster

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=4AFD67C4.9070100@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=jamie@shareable.org \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.