3 ms·
Do you go all the way to Good: “begin”, “end”. Bad: “{“, “}”, “:” ? I’m asking because one can also see keywords as punctuation, adm punctuation tends to be s
by Someone 9y ago
Do you go all the way to
Good: “begin”, “end”. Bad: “{“, “}”, “:”
? I’m asking because one can also see keywords as punctuation, adm punctuation tends to be short. That would make “fn” better than “func” (λ wold be even better, if it were easier to type on common keyboard layouts)
- Sylos 9y agoNot the same guy, but similar feelings, and well, I actually dislike it when programming languages actively declare "function", "begin", "end" or even "X references" (Visual Studio). Because when I read words, I try to assign logical meaning to them. Whereas symbols and whitespace naturally group these logical meanings into contexts. So, having words group the words results in me trying to assign logical meaning to these separator words, and I also just don't find them as clear in separating contexts. Having nothing in a line or just a "{" is much more distinct from actual code than "begin".
- rectang 9y agoI prefer brackets over 'begin' and 'end' for scope, though scope also needs to be reinforced by indentation. However, I'm fine with function/func/def/proc/sub/method (while averse to fn because of pronunciation) -- because those are all types, not punctuation.