On 8/4/05, Derek Lane <[EMAIL PROTECTED]> wrote: > In my case, I have specified to the 1.4 compiler that I want it to > generate code that > will run in a 1.3 JVM. How am I doing so far?
Correct. > A) In some circumstances, based on the specific 1.3 runtime JVM, the > code generated by the 1.4 compiler will not successfully run? Yep. It's not the JVM that is the problem, but the runtime class libraries (rt.jar). The most prevalent example: http://mail-archives.apache.org/mod_mbox/jakarta-commons-dev/200506.mbox/[EMAIL PROTECTED] if you append a stringbuffer, the code compiles in both 1.4 and 1.3, but when compiled on 1.4 it won't run on 1.3 (because append StringBuffer doesn't exist), unless you cast to (Object). > > B) In some cases, based on the code generated by the 1.4 compiler, the > generated code will not successfully run in a 1.3 JVM? I don't see this as different to A? > C) There is a bug in the M2 compiler plugin that will be fixed at some > point, that will enable A dn/or B to work? > Not so much a bug, but a missing feature. To run the other compiler, we need to be able to fork the javac executable in a completely different path to the executing JDK. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
