Earlier quoted context omitted.
Keep in my that in Unicode there are several symbols that look alike. It is not just the character set that matters, but how many of such things we have. May be instead of arguing for Unicode, community needs to come up with a unambiguous smaller set of symbols languages should support.
I dread the day when I edit some code that has both \Sigma and \sum in the same scope.
Sir, Please Step Away from the ASR-33 (2010)
201–210 of 291 posts
Re: Sir, Please Step Away from the ASR-33 (2010)
#202It's a terrible idea. Sooner or later there will be identifiers with homoglyphs. Good luck debugging that!
Re: Sir, Please Step Away from the ASR-33 (2010)
#203Earlier quoted context omitted.
Feel free to reason about a complex statistics formula with full-blown variable names. There are reasons for short variable names. Pass into a specific function a descriptive name of what you do, but do use the mathematically "accepted" writing mode in the implementation of a well-known function.
> There are reasons for short variable names Which are? I suspect the reasons are a combination of the price of paper and ink, the history of teaching using chalkboards. None of those mean we can’t make the canonical version of an equation the expanded representation. Why do we all know e=mc2 and not energy = mass * lightspeed^2. The broader the base of people that have to interact with a formula, the less mathy the…
Re: Sir, Please Step Away from the ASR-33 (2010)
#204My favorite languages don't even have the _idea_ of operators and in languages with custom operators, with all their crazy ass rules about precedence and content-free representations, I'm always re-translating the code to s-expressions in my mind.
The Scheme way seems fine to me - operator-like functions when the meaning is universally understood and then human-readable names for literally everything else.
Re: Sir, Please Step Away from the ASR-33 (2010)
#205> And need I remind anybody that you cannot buy a monochrome screen anymore? Syntax-coloring editors are the default. Why not make color part of the syntax? Why not tell the compiler about protected code regions by putting them on a framed light gray background? Or provide hints about likely and unlikely code paths with a green or red background tint? I'm colorblind, please never do that. Syntax highlighting is fine…
Yeah, I'm a blind coder and having color matter like this does not sound like fun.
Re: Sir, Please Step Away from the ASR-33 (2010)
#206It's a terrible idea. Sooner or later there will be identifiers with homoglyphs. Good luck debugging that!
Supporting unicode doesn't mean you can't defend against homograph attacks. See http://www.unicode.org/reports/tr39/ .
Re: Sir, Please Step Away from the ASR-33 (2010)
#207Earlier quoted context omitted.
OK, I guess that’s a reasonable use of the word “special”. Here is what I was trying to get at: I can not effectively use my computer for anything without customizing the keyboard a little. I need to make the capslock key into an extra control key. I need to set up a compose key so I can type accents when writing in Spanish (even if I didn’t do that, what about writing people's names?). Even sticking with English, I…
This thread is making the point that the issue isn’t the character set, but rather the keyboards. We’re probably locked in, there is so much inertia around the standard QWERTY with a few arrows and Esc. Maybe an integrated system builder with large scale like Apple could shift things slightly.
Re: Sir, Please Step Away from the ASR-33 (2010)
#208Earlier quoted context omitted.
I dread the day when I edit some code that has both \Sigma and \sum in the same scope.
You mean ∑ and Σ? Yeah, that'd be terrible. It doesn't seem like it should be Unicode's job to assign meaning to characters, so I don't know why ∑ ("U+2211 N-Ary Summation") exists.
Re: Sir, Please Step Away from the ASR-33 (2010)
#209Earlier quoted context omitted.
Keep in my that in Unicode there are several symbols that look alike. It is not just the character set that matters, but how many of such things we have. May be instead of arguing for Unicode, community needs to come up with a unambiguous smaller set of symbols languages should support.
And ASCII has the reverse problem: one symbol gets extremely overloaded semantically (syntax wars?!). Tell me what does ":" mean? Now if I tell you the language is Typescript, what does "?" mean? I personally believe semantic overloading causes a lot of problems, but we are so steeped in the existing limitations that we don't recognise it is a problem.
Language overloads things. Pretty much period. I doubt programming will get away from that.
Re: Sir, Please Step Away from the ASR-33 (2010)
#210Earlier quoted context omitted.
And again, this helps other people who have to edit your code how?
Well, if my Julia code ever gets to the point where other people want to edit it, the community has embraced Unicode, so there won’t be a problem there. More generally, I’ll turn my comment into a question: how are people using computers without already having them set up to easily type these characters?
Current solution for most people is google + clipboard
For example, to type the word "cliché" here, I googled it, then copied it, then pasted it.