Re: Multiline comment in Perl

From: "Rob Dixon" <[email protected]>
> (Once again, please bottom-post replies to this group. It maintains 
> readability
> for extended threads. Salutations and signatures should always be edited 
> out.
> You are responsible for the whole of your post, not just your own 
> material.)

Maybe it improves the readability for the sighted, but well... I am blind 
and I usually don't like to parse and read tens of lines until I reach the 
few lines I need.
There is not a single accepted way of posting to a group. On the lists that 
most of the users are Unix/Linux users, the most easy way is to bottom-post, 
and I usually do that, unless I forget that I need to temporary change my 
style, but when I want to send a final message and I don't need any answer 
for it, I use to top-post.

> There are many things that "don't break the program" but are far from good
> programming practice. Start by taking out all whitespace, for example.
> When we think there is very little chance of our code being read by 
> someone else
> or processed in a way we didn't anticipate, the World will surprise us. 
> Being
> nice to the people who expect our program to be Pod-clean is part of the 
> Perl
> ethos, and should be honoured.

As I said, for commenting more lines of text, perl doesn't have a mark, so I 
am not creating a perl documentation. Why should I use a certain style for 
creating a comment?
Other users won't see it, because those comments are usually temporary, 
sometimes used when I don't want to include a piece of code in the program.

> The documentation that John referred you to recommends
>
>  =begin comment
>    :
>  =end

And is this a valid perldoc mark?

> As a last resort you could make a case for not being nice to people and we 
> will
> consider it here.

Please be so kind and explain what do you want to say, because I don't 
understand your phrase. English is not my native language.
Do you want to say that I wasn't kind or that I said something badly to 
someone?

Octavian