Geir Magnusson Jr wrote: > > > Tim Ellison wrote: >> It is available in both Sun and Eclipse compilers (as different names), >> so I'll take that as +1. > > How about IBM?
Yes, I meant 'Sun-derived'. IBM's Java SDK didn't take that option out, and I would expect to see it in BEA's etc too. Regards, Tim >> Of course, as soon as the JCHEVM can understand 1.5-format class files >> we'll drop the target flag. >> >> Regards, >> Tim >> >> Geir Magnusson Jr wrote: >>> >>> Tim Ellison wrote: >>>> As discussed on the list, there is a compiler option in the 5.0 >>>> compilers we use that allows source code containing a subset of Java >>>> 5.0 >>>> language features to be compiled into 1.4 compatible class files. >>>> >>>> Since this is quite a significant change I'd like to get a vote on >>>> whether the project should make this compiler option a necessity for >>>> our >>>> code. >>> I'm scared of tying us to only 1 compiler, although it would be nice to >>> get going on some of the 5.0 features. >>> >>>> The positive outcome of this is that we can develop APIs that rely on >>>> those 5.0 language features, and run the resulting code on existing >>>> 1.4-compatible VMs. >>>> >>>> The downside is that we are using an undocumented compiler feature on >>>> the reference implementation (it is supported on the Eclipse compiler). >>>> >>>> [ ] +1 - Yes, change the build scripts to compile 5.0 code to 1.4 >>>> target >>>> [ ] 0 - I don't care >>>> [ ] -1 - No, don't change the compiler options (please state why) >>> +1 as long as this can be found in both the Sun and Eclipse compilers, >>> >>> -1 if not >>> >>> geir >>> >>> >> > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK.
