3 ms·
The rules for unicode normalization only make a difference when you use them. As an English language programmer, they'll probably never affect you, and you're f
by hyperpape 8y ago
The rules for unicode normalization only make a difference when you use them. As an English language programmer, they'll probably never affect you, and you're free to use your linter to require all code in your projects use only ASCII identifiers, just to prevent any potential problems.
Perl apparently handles this well: you have to declare that a file uses a particular script if you're using non-ASCII identifiers.
- kazinator 8y ago> you have to declare that a file uses a particular script So, no calling functions in other files that use other scripts? A reasonable restriction is to demand that all characters in any one identifier are from the same script, and that purely typographical devices such as ligatures are banned.
- hyperpape 8y agoIf you’re calling from another file you edit the pragmas in the file you’re calling from. Seems easy enough. I actually am not quite clear on the details: one source made it sound like a limited set of scripts was enabled by default. Perhaps someone who knows Perl better can clarify.
- kazinator 8y agoIf I'm in a Japanese file and want to call a function in a Greek file, I don't see how I can avoid writing a Greek identifier in the middle of the Japanese.
- hyperpape 8y agoYou can list multiple scripts: use utf8 ("Greek", "Cyrillic"); This took me a while, but I see how my original post was ambiguous.