Other reasons for the a bit of noise: speed, simplicity and unambiguity of parsing. (Impacts compilation speed, ease of additional tool development, and ability to continue parsing partially incorrect code)
Nim, last I used it a couple of years ago, stopped at the first compilation error. It's not such a bad idea considering errors are usually fixed one-at-a-time.
I'd gladly trade a little compilation speed and ability to continue parsing incorrect code for a syntax without semicolons, braces, and other unnecessary characters. It's one of the things I really like about Python, though even that is starting to add lots of syntaxy glyphs.
prirun|3 years ago
I'd gladly trade a little compilation speed and ability to continue parsing incorrect code for a syntax without semicolons, braces, and other unnecessary characters. It's one of the things I really like about Python, though even that is starting to add lots of syntaxy glyphs.