Talk:Unicode variable names: Difference between revisions

→‎Why!: Not everyone speaks English.
(→‎Why!: time to fix ALGOL back to the way it was)
(→‎Why!: Not everyone speaks English.)
Line 9:
:All this stick-in-the-muddery is kinda beside the point; we'll all have to get used to the future sooner or later. To answer the question behind the question, Perl 6 emphasizes use of Unicode where it enhances readability with traditional (and I don't mean ASCII) symbols. It's arguable whether this helps a great deal with variable names (I think it does in this case), but certainly for operator names it turns what is normally evil, overloading existing operator names, into something that can instead clarify by adding new operator names where the need for visual distinction converges with traditional notations to make that possible. Of course it can be abused, but that's never been a valid argument in Perl culture. Rules that prevent you from writing ugly code also tend to prevent you from writing beautiful code. --[[User:TimToady|TimToady]] 22:25, 6 July 2011 (UTC)
::We could develop a transcoder, using unidecode to convert the source code into portable ascii format and uniencode to adapt the ascii based source for unicode platforms. [[User:Markhobley|Markhobley]] 22:31, 6 July 2011 (UTC)
 
:Not everyone speaks in a language that is adequately conveyed by ASCII. And even in English, some problems are routinely described using non-ASCII characters (just general maths equations comes to mind). We have learnt to convert to ASCII, and may not even notice we are doing it in english, but speakers of other languages might feal more pain. --[[User:Paddy3118|Paddy3118]] 00:11, 7 July 2011 (UTC)
Anonymous user