No, truncation is correct in this case. It's not that the API returns exact binary float representations, it returns prices but somehow decided to use strings as a transport and return fractional cent digits which have been all zero for now but will throw an error in my script because they CANNOT match what's in my database because this in turn stores the prizes as integer cents.
So the context in this specific case calls for truncating as the rounding error seen in my original post was introduced by storing the string representation into a binary float.
I need to use the exact value as returned by the API, not rounded, if the API is off by one cent, it is considered an error.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
