diablo jvm issue, at the byte code level

[Victor Igumnov]

Update, seems like it is a Locale issue, which is odd I remember  
specifically setting it before, and it still produced the same error.  
Well I guess this is user blunder on my part.

How would you set the default locale for the JDK? I might just might  
wrap it around with Spring to set a predefined locale.

-Victor

On Mar 16, 2007, at 8:34 AM, Nick Johnson wrote:

> Surely if it were a bytecode issue, someone else would have been  
> able to
> reproduce it.  As it is, I tried code compiled on FreeBSD, Solaris,
> Windows and Linux and they all worked fine and exactly as expected  
> with
> the testcase.
>
> The one thing that did not work was naming a class "Test" with no  
> package
> name, which I would imagine is a legitimate bug.
>
> Have you tried any of the following:
>
> 	* Running your test on another machine
> 	* Recompiling / Reinstalling the diablo JVM
> 	* CVS Updating your ports and rebuilding the diablo JVM out of
> ports
>
>    Nick
>
> On Fri, 16 Mar 2007, Victor Igumnov wrote:
>
>>> It isn't a Locale issue, seems like a bytecode issue plain and  
>>> simple. If
>>> compiled with the Diablo JVM it works correctly. The reason I  
>>> choose to use
>>> Java for this project is the fact that the bytecode would be  
>>> interchangable
>>> between JVMs/platforms. If I am running into issues this early,  
>>> this makes me
>>> weary.
>>>
>>> -Victor
>>>
>>>
>>>
>>> On Mar 16, 2007, at 1:27 AM, Calvin Varney wrote:
>>>
>>>> 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"
>>>>
>>>
>>
>> _______________________________________________
>> 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"
>>
>
> -- 
> "Humans are a dangerously insane and very sick species."
>    -- Eckhart Tolle
> This message has been brought to you by Nick Johnson 2.2 and the  
> number 6.
> http://healerNick.com/       http://morons.org/        http:// 
> spatula.net/