News for hackers. Stuff that matters.
Re:Language Design: Use 'ident: Type' not 'Type ident' by WalterBright on Friday May 01, 2020 @08:18PM (#23047838)
Being parser-friendly is not at all the same thing as being user-friendly. The difficulty of writing parsers is way overblown.

One thing to avoid is depending on the existence of the symbol table to parse correctly. (C++ has this problem.) Needing a symbol table makes it hard for parsers like source code formatting and syntax highlighting.

Another is to avoid raw string literals that reach back and try to unwind the results of previous "phases of translation".

Re:Language Design: Use 'ident: Type' not 'Type ident' by barrkel on Friday May 01, 2020 @08:24PM (#23047881)
Agree with a caveat; if the syntax has many ambiguities, with resolution solved by a clever parser, it'll be confusing for users, especially newbies, because they'll tend to get errors unrelated to what they were trying to achive.

Redundancy in syntax can be a bonus.

Re:Language Design: Use 'ident: Type' not 'Type ident' by WalterBright on Friday May 01, 2020 @08:32PM (#23047946)
> Redundancy in syntax can be a bonus.

I agree. I even wrote an article about that:

https://www.digitalmars.com/articles/b05.html

Re:Language Design: Use 'ident: Type' not 'Type ident' by seanmcdirmid on Saturday May 02, 2020 @01:42AM (#23049575)
Both humans and computers parse code. Humans can handle ambiguity mode easily than computers, but that doesn’t make the ambiguity more user friendly somehow.