Error/Bug adding floating point numbers

Subjects

•	Home
•	Xalan extension functions
•	Fomatting question serializing DOM with pretty print
•	xalan with pull parser
•	Cannot find the declaration
•	Apache Xalan drop support to run on JRE 1 1 x
•	Why does Doctype change processing of a document
•	Node set to XML string via Java extensions in Xalan J: possible?
•	Templates/Transformers + thread safety???
•	Problem evaluating xpath with muliple prefix with different namespace
•	remove an arbitrary attribute from xsl output
•	Xalan3 XSLT 2 0 XPath 2 0 support?
•	Problem using compiled translets with Xalan !!
•	Xalan and jstl 1 1 problem with transform tag
•	NullPointer in DOM2DTM getLocalName
•	URIResolvers base parameter with xsltc and cascaded imports
•	Performance problem for Xalan J on intel dual core
•	Standard libraries in JAXP?
•	Serializing a DOM tree to XML file, customize entities replacement
•	Library Conflict Involving BCEL Library
•	A question on how users are using <xsl:message >
•	Kevin Cormier as a new Apache Xalan J committer
•	Struggling to iterate over tokenized string
•	Xalan count() trouble
•	Problem with recursive xpath
•	Error when switching to java 1 5
•	document( ' ')
•	Problem with Xalan2 7 0 transformation
•	cr/lf options
•	entity encoded XML
•	can xalan transform 2 xml using one xslt?
•	Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
•	xsl transform with cdata section elements
•	xslt parameters not expanded
•	Weird behavior of XPath evaluate()
•	How to avoid <xsl:message > instruction prints stylesheet file informations ?
•	Cannot find SimpleTransform subdirectory after installing Xalan J
•	recover from document not found exceptions
•	jdk1 5 and Xalan jar differences?
•	Performance Issue
•	Error/Bug adding floating point numbers
•	XPathAPI: eval exp using nodes with default namespace
•	modifying xalan to output invalid XML
•	NullPointerException
•	mege two separate xml nodes into one
•	Is this a XALAN document identification bug?
•	is StylesheetRoot really java io Serializable ?
•	transform() fails for DOMSource but succeeds for StreamSource
•	Thoughts on Transformer parameter passing
•	HELP, Xalan and jstl 1 1 problem with transformer
•	Problem with XPath namespace axis?
•	string utils:replace deleting search string if replacement string is an HTML
•	help with enumeration values pls
•	xalan 2 5 1 vs 2 7 performance question
•	How to insert/update in XML document
•	HTML Serialization and Handling of Ampersands in HREF Attributes
•	XHTML link tag stripping
•	SystemId Unknown; Line #24; Column #49; java lang NullPointerException
•	xpath text() help
•	Apostrophe problem with xalan 2 7 0
•	How to set variables in XML document?

Links

Home

Oracle database error code ...

Error/Bug adding floating point numbers

Error/Bug adding floating point numbers

2006-08-31 - By Timothy Jones

Reply: 1 2 3

I feel your pain, Ambika, really I do...

This is the reason my output stylesheets are riddled with
format-number().

<xsl:value-of select="format-number(number(@(protected)),
'#,##0.00')" />

and

<xsl:variable name='roundedValue'
select='format-number(number($rawValue), "0.00")' />

But in my case, I know I am working with dollars/cents, so I know what
my output precision should be. I fully appreciate that in other cases,
it may not be so clearly defined.

The same kind of behavior exists in languages that have 'float' and
'double' types (C, C++, Java, etc, probably Pascal's "real" type too).
To combat this for currency values, I convert them to the biggest
integer type and process them as cents: 32-bit long in "old C", 64-bit
long in Java, and "long long" on modern C/C++ compilers. At least then
you are in complete control of your math. Java also has
java.math.BigDecimal which doesn't do the IEEE-754 behavior either, but
it has the overhead of being a java.lang.Object subclass, whereas the
primitive integers/longs work faster.

I have never understood how people can accept this rounding over the
years, but these are my workarounds.

Timothy Jones

Syniverse Technologies

Work

(813) 637-5366

Sr. Systems Engineer

Cell

(813) 857-7650

Development, Tampa, FL

<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas
-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office
:smarttags" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=blue>

<div class=Section1>

I feel your pain, Ambika, really I do...<o
:p></o:p>

<o:p> </o:p>

This is the reason my output stylesheets
are riddled with format-number().<o:p></o:p>

<o:p> </o:p>

       &nbsp
;<xsl:value-of
select="format-number(number(@(protected)), '#,##0.00')" /><o:p><
/o:p>

and<o:p></o:p>

       &nbsp
;<xsl:variable
name=’roundedValue’ select=’format-number(number($rawValue),
“0.00”)’
/><o:p></o:p>

<o:p> </o:p>

But in my case, I know I am working with
dollars/cents, so I know what my output precision should be.  I fully
appreciate that in other cases, it may not be so clearly defined.<o:p></o:p>

<o:p> </o:p>

The same kind of behavior exists in
languages that have ‘float’ and ‘double’ types (C, C++,
Java, etc, probably Pascal’s “real” type too).  To
combat this for currency values, I convert them to the biggest integer type and
process them as cents: 32-bit long in “old C”, 64-bit long in Java,
and “long long” on modern C/C++ compilers.  At least then you
are in complete control of your math.  Java also has java.math.BigDecimal
which doesn’t do the IEEE-754 behavior either, but it has the overhead of
being a java.lang.Object subclass, whereas the primitive integers/longs work
faster.  <o:p></o:p>

<o:p> </o:p>

I have never understood how people can
accept this rounding over the years, but these are my workarounds.<o:p></o:p>

<o:p> </o:p>

<o:p> </o:p>

<div>

<table class=MsoTableGrid border=0 cellspacing=0 cellpadding=0
style='border-collapse:collapse'>
<tr>
<td width=180 colspan=2 valign=top style='width:134.85pt;padding:0in 5.4pt
0in 5.4pt'>
Timothy 
 Jones<o:p></o:p>
</td>
<td width=419 valign=top style='width:314.6pt;padding:0in 5.4pt 0in 5.4pt'>
Syniverse
Technologies<o:p></o:p>
</td>
</tr>
<tr>
<td width=60 valign=top style='width:44.85pt;padding:0in 5.4pt 0in 5.4pt'>
Work<o:p></o:p>
</td>
<td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
(813) 637-5366<o:p></o:p>
</td>
<td width=419 valign=top style='width:314.6pt;padding:0in 5.4pt 0in 5.4pt'>
Sr. Systems Engineer  <o:p></o:p>
</td>
</tr>
<tr>
<td width=60 valign=top style='width:44.85pt;padding:0in 5.4pt 0in 5.4pt'>
Cell<o:p></o:p>
</td>
<td width=120 valign=top style='width:1.25in;padding:0in 5.4pt 0in 5.4pt'>
(813) 857-7650<o:p></o:p>
</td>
<td width=419 valign=top style='width:314.6pt;padding:0in 5.4pt 0in 5.4pt'>
Development, <st1:place w:st="on"><st1
:City
w:st="on">Tampa</st1:City>, <st1:State w:st="on">FL</st1:State></st1:place><o:p></o:p>
</td>
</tr>
</table>

</div>

<div>

<o:p> </o:p>

</div>

</div>

</body>

</html>