Re: Target VM Microsoft? or Java Lint to check for MS VM compatibility?

From: Vincent Cate (vince_at_offshore.ai)
Date: 12/19/03 

Date: 19 Dec 2003 12:38:57 -0800

Chris Smith <cdsmith@twu.net> wrote in message news:<MPG.1a4cc749902e95f298984c@news.pop4.net>...
> Vincent Cate wrote:
> > 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.
>
> The Java API version 1.1 also doesn't have Vector.add() The
> java.util.List-based names for Vector functions were only added with the
> advent of the Collections API in 1.2. I'm guessing, then, that you only
> think you are doing that, and that you aren't really doing it at all.

I just checked again and in my JBuilder I have "target VM: All Java SDKs"
which I thought makes things that are 1.1 compatible. Other choices are
"Java 2, v 1.2 and later", as well as 1.3, and 1.4. Maybe I am only
compatible with "Java 2, v 1.1" and Microsoft is at "Java 1, v 1.1"?
Or is JBuilder is goofing up? Or am I confused about something else?

> When I said Microsoft is short a few APIs from 1.1, I didn't mean
> something so fundamental as Vector. I think I recall something about
> RMI, something about JNI, and something about minor details of
> reflection.

Using Vector.addElement() works fine, so it is not that they don't
have Vector.

  -- Vince

Relevant Pages