Hi Adam, My apologies, this was a misunderstanding on my part. I think I misread this comment <https://mail.openjdk.org/pipermail/core-libs-dev/2024-August/127983.html> and didn't notice the word "preview":
Unfortunately, ClassFile API's scope is only to interpret correctly the > Class Files that are accepted by the current VM and support writing such > class files; for example, for release N, we will not support correct > parsing or writing of *preview* class files from N-1, N-2, etc. So I mistakenly thought it was saying the ClassFile API in JDK N would not support class files from previous versions N-1, etc. -Archie On Wed, Aug 28, 2024 at 2:13 AM Adam Sotona <adam.sot...@oracle.com> wrote: > Class files conforming to the Chapter 4. “The class File Format” of the > Java Virtual Machine Specification are supported. It covers class file > versions far to the history. > > > > Feel free to report cases where the support is insufficient. > > > > Thank you, > > Adam > > > > *From: *Archie Cobbs <archie.co...@gmail.com> > *Date: *Tuesday, 27 August 2024 at 18:49 > *To: *core-libs-dev@openjdk.org <core-libs-dev@openjdk.org> > *Cc: *Adam Sotona <adam.sot...@oracle.com>, jdk-...@openjdk.org < > jdk-...@openjdk.org> > *Subject: *[External] : Re: New candidate JEP: 484: Class-File API > > Question... would it be appropriate for this JEP to mention that support > for older-than-current classfile versions is an explicit non-goal? > > > > Otherwise I think there could be many repeats of this discussion > <https://mail.openjdk.org/pipermail/core-libs-dev/2024-August/127982.html> > from the other day. > > > > To be clear, I don't disagree with the design choice, I just think it > might be worthwhile to address that point directly and clarify the thinking > behind it so there's no ambiguity. > > > > As it's written today, a casual reading of the JEP comes across as if > we're talking about a great new JDK-sanctioned tool with state of the art > design that will help get all of the classfile manipulation libraries on > the same page to allow analysis/transformation of any class file on the > classpath. Or at least, it doesn't do anything to dispel that notion > (unless I'm missing something). > > > > -Archie > > > > On Tue, Aug 27, 2024 at 8:58 AM Mark Reinhold <mark.reinh...@oracle.com> > wrote: > > https://openjdk.org/jeps/484 > > Summary: Provide a standard API for parsing, generating, and > transforming Java class files. > > - Mark > > > > -- > > Archie L. Cobbs > -- Archie L. Cobbs
