> LISP/Scheme, where block comments were never a thing (I think.)
Lisp does have block comments,
#| This is a block comment |#
You can also use feature expressions to effectively comment out code #+(or)
(defun foo ...)
The reader will skip over the following sexp if the feature expression isn't true (and `(or)` never is).
Re:Block Comments Are a Bad Idea
by steveklabnik on Wednesday October 11, 2017 @10:12AM
(#15449900)
Incidentally, Ruby has block comments, but almost nobody knows about them, because they're inherited from Perl. Ruby comments are line comments with #, but you can also use =begin and =end for block comments.
See also GOTO which is a wart 99.9% of the time but really useful for writing e.g. parsers.
Error handling.
Re:Block Comments Are a Bad Idea
by johannes1234321 on Wednesday October 11, 2017 @08:11AM
(#15449087)
In most languages there are better way to do this than goto. Among them
- extracting code into smaller functions (yes, state has to passed around)
- exceptions (yeah yeah, hate them or love them, but if used in your environment it makes sense not to avoid them)
- RAII pattern or handling cleanup, which allows simple return and "automatic" resource handling
- etc.
True, in a language like C these don't apply necessarily and goto still has some use -
For blocks comments in a functional language though, it might work because many people would come from LISP/Scheme, where block comments were never a thing (I think.)