Re: Acme::Comment -- Module Review

[jweed]

I think multi-line commenting (a single format of) would be great implemented as a standard feature in a future version of Perl; perhaps in Perl6? (it can't hurt to hope)

It isn't happening. Basically, they're going to try to redo POD so it's all spiffy, but Lwall gives the multi line comment RFC a rejection. So it looks like it isn't going to happen.

From Apocalypse 2:

But even if I weren't blindly prejudiced, I suspect I'd look at the psychology of the thing, and notice that much of the time, even in languages that have multiline comments, people nevertheless tend to use them like this:

    /*
     *  Natter, natter, natter.
     *  Gromish, gromish, gromish.
     */

The counterargument to that is, of course, that people don't always do that in C, so why should they have to do it in Perl? And if there were no other way to do multiline comments in Perl, they'd have a stronger case. But there already is another way, albeit one rejected by this RFC as "a workaround."

(In response to RFC 5)

Edit by tye, preserve formatting

[Aristotle]

Although I must say I find the syntax

#<<END_COMMENT
blah
blah
blah
END_COMMENT

quite appealing in its consequence. Pity that Acme::Comment doesn't support that style.

[wazoox]

I strongly agree with Apo2, because I myself never use the /* */ comment and always the C++ // comments (yes I know it's bad).

Another thing comes to my mind: whenever I want a multiline comment REALLY HARD, it usually proves to be some form of documentation, so I end up writing an inline POD paragraph instead.

inline POD rules! :)