Timeline for Are there historical problems with non-ASCII identifier characters in code?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2022 at 16:50 | comment | added | JacquesB | @GregBurghardt: Sure, but then you are limited to developers having that native language and keyboard. You can't easily use international developers or outsource. This just limits your options. Code style recommendation is usually there to reduce friction and risk, and this is an avoidable problem. | |
| Jan 29, 2022 at 23:25 | comment | added | Michael Macha | Doppelganger characters are really standing out for me here as a potential problem; I'm generally talking about going from a formula on a whiteboard to executable code. I might be wrong about having used it in Python 2, I haven't used it in quite some time. (Ideally, I never will again...) but yeah, speaking the same cultural context is definitely critical for a lot of different reasons. | |
| Jan 29, 2022 at 21:18 | comment | added | amon | I've definitely used Unicode identifiers (a) in teaching contexts for people who don't speak English natively, (b) in domain specific contexts where ASCII transliterations would obfuscate the code – sometimes, making the code look like a typeset formula is more important than being able to type or change the code. But that's pretty rare. | |
| Jan 29, 2022 at 20:42 | comment | added | Greg Burghardt |
I'm not sure if typing ã is a big deal for some people. If their language uses it, they may have different keyboards than we have in the USA.
|
|
| Jan 29, 2022 at 17:11 | history | answered | JacquesB | CC BY-SA 4.0 |