Re: Double value Xml parsing issue

2007-10-18 Thread krushna sahoo
giv me ur number and location :) On 10/18/07, Rinilkumar [EMAIL PROTECTED] wrote: Yes u can call me dear - Original Message - *From:* krushna sahoo [EMAIL PROTECTED] *To:* c-dev@xerces.apache.org *Sent:* Thursday, October 18, 2007 12:31 PM *Subject:* Double value Xml parsing

Re: Double value Xml parsing issue

2007-10-18 Thread Boris Kolpackov
Hi Krushna, krushna sahoo [EMAIL PROTECTED] writes: I have some double value e.g 1937.966 in xml file, but after parsing through SAX2XMLReader XMLReaderFactory my application getting it as 1937.95799, which is wrong for my application. Are you converting the text representation to the double

[jira] Resolved: (XERCESC-1752) pattern match failure in restriction of decimal

2007-10-18 Thread Boris Kolpackov (JIRA)
[ https://issues.apache.org/jira/browse/XERCESC-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boris Kolpackov resolved XERCESC-1752. -- Resolution: Fixed Fix Version/s: 2.8.0 Fixed in 2.8.0. pattern match

Re: Double value Xml parsing issue

2007-10-18 Thread Axel Weiss
On Thu, 2007-10-18 at 10:12 +0200, Boris Kolpackov wrote: 1937.966 not being representable by double so you get the next closest value. Boris, this is not true. When I print out the original value 1937.966 in different IEEE floating point representations, I get the following results: as double

2.8.0 and 3.0.0 added to Jira

2007-10-18 Thread Boris Kolpackov
Hi, The just released 2.8.0 and upcoming 3.0.0 versions were added to Jira. Please use 3.0.0 to schedule issues that you want fixed for this version. Boris -- Boris Kolpackov Code Synthesis Tools CC http://www.codesynthesis.com Open-Source, Cross-Platform C++ XML Data Binding

Re: Offer to update the build documentation at http://xerces.apache.org/xerces-c/build-winunix.html

2007-10-18 Thread Boris Kolpackov
Hi Justin, Justin Dearing [EMAIL PROTECTED] writes: Personally I don't mind making changes that will last a couple of months. Secondly, I think that even if the cygwin and mingw directions were shortened to see unix directions in version 3.0, making that explicitly clear, and organizing the