4 ms·
It's easier to parse, especially if your language has lots of keywords that might be part of identifiers, like "begin", "end", "for" and "and" or "or". I think
by mhd 6y ago
It's easier to parse, especially if your language has lots of keywords that might be part of identifiers, like "begin", "end", "for" and "and" or "or". I think with the Algol-like languages it was mostly required to specially treat the keywords, either by quoting them, uppercasing them or writing them in bold (if supported).
But beyond that, I'm not sure that I want that in a "modern" idiom, where I get a whole bunch of compound words on the screen, like classes, objects, methods and variables. Spaces are quite easy to pick out as delimiters -- and I've actually heard that as an argument for CamelCase against snake_case.
Then again, I'm German so I might have a high tolerance for long strings and syntactical pain.
- QuesnayJr 6y agoChange frightens me, so I find the idea of spaces in identifies shocking, but I'm curious if once you got used to the idea if there are upsides. Especially now with syntax highlighting, you could visually tell whether it was distinguishing keywords from your identifiers correctly.
- retrac 6y ago> Then again, I'm German so I might have a high tolerance for long strings and syntactical pain. You're certainly used to stropping your Nouns. Maybe `all` that `keyword` stropping `in` ALGOL 60 isn't so bad `if` you're used to that. 8-)