<div dir="ltr"><div dir="ltr">On Mon, Feb 20, 2023 at 12:26 PM David Alayachew <<a href="mailto:davidalayachew@gmail.com">davidalayachew@gmail.com</a>> wrote:</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">>Â yes your idea would solve the problem, but at the expense of backward compatibility.<div dir="auto"><div dir="auto"><br></div><div dir="auto">Could you explain how the solution is backwards incompatible? I don't think I understand.</div></div></div></blockquote><div><br></div><div>You're talking about changing the mapping that takes a Java class name and returns the corresponding filename for that class' classfile in the filesystem. This means classes that used to load successfully would suddenly fail to load because the file would no longer be found.</div><div><br></div><div>Even if you tried to use some kind of fallback scheme, you'd still be potentially creating filename clashes with other classes, etc.<br></div><div>Â </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto"><div dir="auto">> As Jon points out that would be "an incompatible change of seismic proportions".</div><div dir="auto"><br></div><div dir="auto">I think I missed Jon's comment. Could you paste/link his comment here?</div></div></div></blockquote><div><br></div><div><a href="https://mail.openjdk.org/pipermail/compiler-dev/2023-February/022232.html">https://mail.openjdk.org/pipermail/compiler-dev/2023-February/022232.html</a></div><div><br></div><div>-Archie<br></div></div><br>-- <br><div dir="ltr" class="gmail_signature">Archie L. Cobbs<br></div></div>