diablo jvm issue, at the byte code level

[Calvin Varney]

This could be a locale problem rather than a Diablo jvm one. What
happens if you specify the local when invoking getCurrencyInstance, e.g.
NumberFormat.getCurrencyInstance(Locale.US);

See
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/using-localization.html for setting you locale.

cheers

Calvin.

On Thu, 2007-03-15 at 14:25 -0700, victori at salesdepotinc.com wrote:
> Anonuser has posted on my behalf, seems like this issue with  
> NumberFormat is at the bytecode level
> 
> Here is an example testcase:
> 
> import java.text.*;
> 
> public class Test {
>     public static void main(String[] args) {
>      try {
>       System.out.println(NumberFormat.getCurrencyInstance().parse 
> ("$1.99").doubleValue());
>      } catch (Exception e) {
>       e.printStackTrace();
>      }
>     }
> }
> 
> Save as Test.java ; compile under the SUN JVM:  javac Test.java
> 
> 
> Run the class under the Diablo jvm and you will receive
> 
> -bash-2.05b$ java Test
> java.text.ParseException: Unparseable number: "$1.99"
>          at java.text.NumberFormat.parse(NumberFormat.java:309)
>          at Test.main(Test.java:6)
> 
> And when I run it with the SUN JDK
> 
> absolute# /usr/local/linux-sun-jdk1.5.0/bin/java Test
> 1.99
> 
> 
> Works correctly.
> 
> 
> _______________________________________________
> freebsd-java at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-java
> To unsubscribe, send any mail to "freebsd-java-unsubscribe at freebsd.org"