Hi Tom,
Of course you should consider that the programmer may be block commenting a
section of code precisely because it does contain sytax errors. I often do
so as a way of isolating hard to track bugs. I can't imagine how getting
more courteous error messages would be a Good Thing!
Lets face it -- comments in general are a luxury. Certainly "#" could be
eliminated from Perl and people could all invent workarounds using POD, or
stuff like $comment="check counter variable here" in their code. I just
don't understand why folks are so opposed to real block comments like other
languages have (yeh yeh, I know).
The way I see it Santa (aka Larry) has asked for our wish list. This is not
the time to dwell on all the ways we can make due with our old toys.
--Michael
PS I'm all for a new list. How do I get one?
----- Original Message -----
From: "Tom Christiansen" <[EMAIL PROTECTED]>
To: "Michael Mathews" <[EMAIL PROTECTED]>
Cc: "Nick Ing-Simmons" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, August 02, 2000 5:33 PM
Subject: Re: multiline comments
> >> What is wrong with
> >>
> >> if (0) {
> >>
> >> }
>
> >1) what if the block contains syntax errors?
>
> Then the compiler carefully and courteously notifies you of such.
>
> >2) what if the bloack contains unmatched braces?
>
> See above.
>
> >3) this is not easier to type or remember than the currently available
> >workarounds.
>
> Au contraire. It's *TRIVIAL* to remember, as it requires no new syntax
> and hacks and features and scoot-arounds. Likewise most of the rest
> of them.
>
> --tom
