News for hackers. Stuff that matters.
Re:Block Comments Are a Bad Idea by jstewartmobile on Wednesday October 11, 2017 @08:33AM (#15449197)
I will second this from bitter experience.

Was translating a very old Pascal program. My editor didn't have syntax highlighting for it. Spent a couple hours translating a very large function. Wasn't until I finished that I realized it was wrapped in a very large block comment.

That, and most decent editors have a "comment current selection" feature that makes single-line comments easy enough.

Re:Block Comments Are a Bad Idea by RobertJacobson on Wednesday October 11, 2017 @08:46AM (#15449278)
Why do you fault multiline comments and not your code editor?
Re:Block Comments Are a Bad Idea by jstewartmobile on Wednesday October 11, 2017 @02:09PM (#15451832)
Colors don't feel as robust to me as syntax.

   * color blindness
   * broken syntax above typically throws-off subsequent highlighting
   * touch a lot of embedded stuff where having any kind of editor at all (even without highlighting) is a luxury
Re:Block Comments Are a Bad Idea by barrkel on Wednesday October 11, 2017 @08:45AM (#15449269)
Decent editors have lexical highlighting as well as commenting selection; this argument cancels itself out.

Personally I like having two block comment syntaxes to choose from, like Pascal's { } and (* * ); normal comments use { }, while if you want to comment out an entire block of the program and not have the comment terminate early, use (* and * ).

Most of my professional life editing Pascal code was done from command-line editors that didn't have support for commenting the current selection, other than piping the selection through a command like sed. I appreciated being able to narrow down bugs using (* and *).