<div dir="ltr"><div>Hi Adam,</div><div><br></div><div>My apologies, this was a misunderstanding on my part. I think I misread <a href="https://mail.openjdk.org/pipermail/core-libs-dev/2024-August/127983.html">this comment</a> and didn't notice the word "preview":</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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 <b>preview</b> class files from N-1, N-2, etc.</blockquote><div><br></div><div>So I mistakenly thought it was saying the ClassFile API in JDK N would not support class files from previous versions N-1, etc.<br></div><div><br></div><div>-Archie<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 28, 2024 at 2:13 AM Adam Sotona <<a href="mailto:adam.sotona@oracle.com">adam.sotona@oracle.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg1027915217940276244">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_1027915217940276244WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">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.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Feel free to report cases where the support is insufficient.<u></u><u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt"><u></u> <u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:11pt">Thank you,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Adam<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<div id="m_1027915217940276244mail-editor-reference-message-container">
<div>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentcolor currentcolor;padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-bottom:12pt"><b><span style="color:black">From:
</span></b><span style="color:black">Archie Cobbs <<a href="mailto:archie.cobbs@gmail.com" target="_blank">archie.cobbs@gmail.com</a>><br>
<b>Date: </b>Tuesday, 27 August 2024 at 18:49<br>
<b>To: </b><a href="mailto:core-libs-dev@openjdk.org" target="_blank">core-libs-dev@openjdk.org</a> <<a href="mailto:core-libs-dev@openjdk.org" target="_blank">core-libs-dev@openjdk.org</a>><br>
<b>Cc: </b>Adam Sotona <<a href="mailto:adam.sotona@oracle.com" target="_blank">adam.sotona@oracle.com</a>>, <a href="mailto:jdk-dev@openjdk.org" target="_blank">jdk-dev@openjdk.org</a> <<a href="mailto:jdk-dev@openjdk.org" target="_blank">jdk-dev@openjdk.org</a>><br>
<b>Subject: </b>[External] : Re: New candidate JEP: 484: Class-File API<u></u><u></u></span></p>
</div>
<div>
<div>
<p class="MsoNormal">Question... would it be appropriate for this JEP to mention that support for older-than-current classfile versions is an explicit non-goal?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Otherwise I think there could be many repeats of <a href="https://mail.openjdk.org/pipermail/core-libs-dev/2024-August/127982.html" target="_blank">
this discussion</a> from the other day.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">-Archie<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 27, 2024 at 8:58<span style="font-family:"Arial",sans-serif"> </span>AM Mark Reinhold <<a href="mailto:mark.reinhold@oracle.com" target="_blank">mark.reinhold@oracle.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentcolor currentcolor currentcolor rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><a href="https://openjdk.org/jeps/484" target="_blank">https://openjdk.org/jeps/484</a><br>
<br>
Summary: Provide a standard API for parsing, generating, and<br>
transforming Java class files.<br>
<br>
- Mark<u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
<span class="m_1027915217940276244gmailsignatureprefix">-- </span><u></u><u></u></p>
<div>
<p class="MsoNormal">Archie L. Cobbs<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div></blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Archie L. Cobbs<br></div>