harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig Blake <craigwbl...@mac.com>
Subject Re: [vote] Require compiler options that allow partial 5.0 language features
Date Sun, 19 Mar 2006 18:03:28 GMT
Wow, you learn something new every day.  That's very cool, indeed.   
Thanks for the info.

Craig Blake

On Mar 19, 2006, at 9:50 AM, Tim Ellison wrote:

> Craig,
>
> You are right, the target for Sun-based compilers is "jsr14" (but it
> means the same thing)
>
> See:
> http://mail-archives.apache.org/mod_mbox/incubator-harmony-dev/ 
> 200603.mbox/%3c4419738E.9010704@googlemail.com%3e
>
> Regards,
> Tim
>
> Craig Blake wrote:
>> Correct me if I am wrong, but I don't think the Sun compiler actually
>> lets you specify the source as 1.5 and the target as 1.4; every  
>> version
>> of the 1.5 compiler I have tried that on gives an error:
>>
>> javac: source release 1.5 requires target release 1.5
>>
>> So, it seems that relying on that particular combination of  
>> options will
>> rule out building Harmony on the Sun SDK.  Of course, I am on OSX, so
>> maybe one of the newer Sun 1.5 releases finally has it enabled.
>>
>> Craig Blake
>>
>> On Mar 19, 2006, at 7:04 AM, Tim Ellison wrote:
>>
>>> It is available in both Sun and Eclipse compilers (as different  
>>> names),
>>> so I'll take that as +1.
>>>
>>> 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 (t.p.ellison@gmail.com)
>>> IBM Java technology centre, UK.
>>
>>
>
> -- 
>
> Tim Ellison (t.p.ellison@gmail.com)
> IBM Java technology centre, UK.


Mime
View raw message