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

[Jonathan Gibbons]

On 2/19/23 3:55 AM, David Alayachew wrote:
> Hello Compiler-Dev Team,
>
> I have seen a lot of recent discussions about class names and how the 
> compiler should generate them (or fail with an error). Seeing that, I 
> wanted to query the group and see if anyone has the bandwidth to look 
> at this and give some insight.
>
> https://bugs.openjdk.org/browse/JDK-8287885
>
> The developer assigned labeled it as an enhancement, but I don't see 
> how. I reached out to the developer and tried to contest it, but 
> received no response.
>
> Could someone take another look at this bug and give me some insight 
> on what this bug should be classified as and why?
>
> Thank you for your time and help!
> David Alayachew


JLS 2 contained the following text suggesting that file names could be 
encoded in some way:

---
A package name component or class name might contain a character that 
cannot correctly appear in a host file system's ordinary directory name, 
such as a Unicode character on a system that allows only ASCII 
characters in file names. As a convention, the character can be escaped 
by using, say, the @ character followed by four hexadecimal digits 
giving the numeric value of the character, as in the \uxxxx escape 
(§3.3), so that the package name:

children.activities.crafts.papierM\u00e2ch\u00e9

which can also be written using full Unicode as:

children.activities.crafts.papierMâché

might be mapped to the directory name:

children/activities/crafts/papierM at 00e2ch@00e9

If the @ character is not a valid character in a file name for some 
given host file system, then some other character that is not valid in a 
identifier could be used instead.

---


However, the text is not in JLS 3 and that ship has effectively sailed. 
Changing the filename usage would be an incompatible change of seismic 
proportions across the entire ecosystem.

-- Jon