4 ms·
From my own experience with it: - .class files compiled on Apple's JVM work fine on other JVMs - Source code written for Apple's version of javac will compile
by pmjordan 16y ago
From my own experience with it:
- .class files compiled on Apple's JVM work fine on other JVMs
- Source code written for Apple's version of javac will compile fine on other Java compilers.
To my knowledge, Microsoft's JVM violated both of these requirements, which was Sun's bone of contention. (Android's Dalvik is in similar violation, but doesn't pretend to be "Java" - they're being sued based on patents IIRC)
- acqq 16y ago> .class files compiled on Apple's JVM work fine on other JVMs Technically, you don't need to compile "on JVM" but "for JVM." And it doesn't seem to be as you describe for most of the cases (in Sun's words, 98%). > Microsoft's JVM violated both of these requirements AFAI understand it was far more subtle: the language (the source form representation) was extended with the features which functioned only on Microsoft's implementation, and only such classes were affected. See http://download.oracle.com/javase/1.4.2/docs/guide/deployment/deployment-guide/upgrade-guide/ http://download.oracle.com/javase/1.4.2/docs/guide/deploymen... for a list of issues of switching from Microsoft VM based upon Java 1.1 to Sun's 1.4.2. The list appears to be very unimpressive.