Hi Pekka,
Please think about the reasons for upgrading Classpath source from 1.3 to 1.5
(without intermediate 1.4) in the past - they were (roughly saying) more strict
compiler checking and ability to launch apps using annotations at runtime.
If you could show the community that upgrading to 1.7 brings some benefit
(e.g., like above) then it is ok to upgrade to 1.7 directly (thus eliminating
Classpath VM implementors efforts to verify with 1.6).
As for me, both of our 2 VM implementations still stay on Classpath 0.93 (with
a lot of patches) because it requires significant efforts to fully upgrade to
VM 1.5 API.
Regards,
Ivan
Sat, 13 Oct 2012 10:19:17 +0300 от Pekka Enberg <penb...@kernel.org>:
>
>
>
>
>On Sat, Oct 6, 2012 at 7:20 AM, Andrew Hughes <ahug...@redhat.com> wrote:
>
> I was going to ask the same. I don't see any good reason to change this.
>
>
Fair enough. What needs to happen for us to move on to 1.7 and
>
eventually 1.8 which both have classfile format and language changes?
>
>
