News for hackers. Stuff that matters.
Re:Perl Cannot Be Parsed: A Formal Proof by andreyf on Thursday August 13, 2009 @02:21PM (#761376)
Meh, "defective" is a strong word. It really depends on what you want out of your language - if you want static code analysis or a macro system, then yes, it's defective. If you're looking to write a language that people use to write scripts here and there, then it's just a question of taste.
Re:Perl Cannot Be Parsed: A Formal Proof by tolmasky on Thursday August 13, 2009 @02:38PM (#761414)
Yes, but for a more practical example, this is defective in that it cannot be syntax highlighted correctly.
Re:Perl Cannot Be Parsed: A Formal Proof by mst on Thursday August 13, 2009 @04:19PM (#761616)
Hacky perl can't be highlighted

Sensibly written perl highlights just fine - and you really need to commit intentional pathology to break the modern vim/emacs/etc. highlighters.

Personally I find syntax highlighters less helpful and more annoying than the wavy green line grammar check in word, but as a consultant I get to use editors with highlighting often enough and don't remember the last time I broke one ...

Re:Perl Cannot Be Parsed: A Formal Proof by barrkel on Thursday August 13, 2009 @02:48PM (#761440)
And syntax highlighting normally only requires lexical analysis, not syntactic analysis.
Re:Perl Cannot Be Parsed: A Formal Proof by alxv on Thursday August 13, 2009 @03:33PM (#761520)
Conversely, automatic indentation requires syntactic analysis.
Re:Perl Cannot Be Parsed: A Formal Proof by barrkel on Saturday August 15, 2009 @07:32PM (#765363)
However, most pretty printers only perform lexical analysis.