Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?
From: Vincent Cate (vince_at_offshore.ai)
Date: 12/19/03
- Next message: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Previous message: Todd Prickett: "Building a menubar question"
- In reply to: Tim Tyler: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Next in thread: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Reply: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 19 Dec 2003 06:48:07 -0800
tom.cowdery@bigfoot.com (Tom)
> Until then, compile to version 1.1 and you should be OK.
I do that and it is not OK. Microsoft does not have Vector.add()
for example. Maybe it "should be OK" but lawyers can argue that.
Chris Smith (cdsmith@twu.net)
>I seem to recall that Microsoft is even a few APIs short of 1.1, but
>I don't remember the details.
Yes, they are a few short. My problem is that JBuilder does not help
me avoid these few.
Québec (notAgain@enough.ca)
>I have played a lot with that and I recomend: stay with Microsoft
>jvm, jvc.exe, jview.exe.
If I test under Microsoft's jvm, and I test everything, I could find out
if there are problems. But I would like for either my compiler or
some other tool to just warn me not to use things Microsoft does
not have. Also, it is not easy to see what is wrong at least when
I have run it from a browser. If it does not have the byte code
for Vector.add() it does not print out an error message saying
"Microsoft does not support Vector.add()" as it just does not
recognize the byte code.
Tim Tyler:
>You probably don't need their SDK to test on their JVM.
>
>...but you *do* need to test on their JVM if you want to run there.
If my compiler (or some lint type tool) could tell me what methods
I had to avoid, I don't think I would have to test on their JVM,
at least for the problems I have seen.
I don't mind avoiding methods that Microsoft does not have in their
JVM, but it seems wrong to have to use their SDK. I like
JBuilder's "target all JDKs" so I can only use things on JDK 1.1
and I get warnings of anything "deprecated" in future JDKs.
Still looking for a "Java portability lint" ...
-- Vince
- Next message: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Previous message: Todd Prickett: "Building a menubar question"
- In reply to: Tim Tyler: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Next in thread: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Reply: Chris Smith: "Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|