Timeline for Are there historical problems with non-ASCII identifier characters in code?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2022 at 13:38 | comment | added | gnasher729 | For example, the MacOS file system states explicitly which Unicode version is used to compare filenames. (The reason: What is today an "unassigned character" might next year be "letter z with cedilla" as a random example. But you don't want to change whether two files stored on your hard drive have the same or different names, so when. that character gets defined, it will be treated as different in the file system). | |
| Jan 30, 2022 at 13:30 | comment | added | jpa | @gnasher729 Unfortunately the rules also change over time as new versions of Unicode standards get published. | |
| Jan 30, 2022 at 12:44 | comment | added | gnasher729 | Would be great if all tools followed the Unicode rules correctly. I think publishing a fast and correct and fast algorithm to implement .equals(), .hasprefix() and .hassuffix() would be nice. | |
| Jan 30, 2022 at 7:58 | history | answered | jpa | CC BY-SA 4.0 |