Could someone take another look at my submitted bug regarding class names?

[David Alayachew]

Hello Archie,

Thank you for your response, and apologies on the delay in mine.

I definitely understand what you are talking about now. I also see why you
were considering the zip file solution earlier on.

I will give this some thought and prototype some ideas, but it definitely
looks like there isn't a clean way out of this. Still, this answers my
question and gives a lot of clarity for how the compiler creates .class
files.

Thank you for your help and insight!
David Alayachew

On Mon, Feb 20, 2023, 1:32 PM Archie Cobbs <archie.cobbs at gmail.com> wrote:

> On Mon, Feb 20, 2023 at 12:26 PM David Alayachew <davidalayachew at gmail.com>
> wrote:
>
>> > yes your idea would solve the problem, but at the expense of backward
>> compatibility.
>>
>> Could you explain how the solution is backwards incompatible? I don't
>> think I understand.
>>
>
> 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.
>
> Even if you tried to use some kind of fallback scheme, you'd still be
> potentially creating filename clashes with other classes, etc.
>
>
>> > As Jon points out that would be "an incompatible change of seismic
>> proportions".
>>
>> I think I missed Jon's comment. Could you paste/link his comment here?
>>
>
> https://mail.openjdk.org/pipermail/compiler-dev/2023-February/022232.html
>
> -Archie
>
> --
> Archie L. Cobbs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/compiler-dev/attachments/20230318/359ff550/attachment.htm>