[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JamVM 1.1.3 released
From: |
Archie Cobbs |
Subject: |
Re: JamVM 1.1.3 released |
Date: |
Tue, 13 Apr 2004 12:34:14 -0500 (CDT) |
Robert Lougher wrote:
> Yes, I know :) I couldn't decide whether it was a good idea to slavishly
> follow Sun's options or not. The -X (as you're obviously aware) means
> "non-standard options", and includes -Xms and -Xmx which I also do not have
> an X in front of (as used to be in JDK 1.1.x). Also, on Sun's VM,
> -classpath is specified as -classpath xxx:yyy whereas -Xbootclasspath is
> -Xbootclasspath:xxx:yyy which is (in my mind anyway) confusing. On JamVM
> it's -bootclasspath xxx:yyy (added in 1.1.1), so I'd have had to change that
> as well.
>
> CC'ing to the mailing list, as I'm interested in other people's opinions on
> this!
I think as a practical matter it's a good idea to support some of
the more obvious flags like "-classpath".. however, full compatibility
is probably not worth the trouble.
Also, note that the specification for these flags is part of the
JNI invocation interface, and there is no specification (that I
know of) for the java(1) command line itself. Sun apparently just
copies over the command line flags into the JNI_CreateJavaVM() call,
which is why they look the same.
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com