Octavian Rasnita wrote: > > 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.
I am sighted. I don't know what method you use to read newsgroup posts, but if it doesn't allow you to skip to the unquoted part of a post then I am sure there is something better available. Perhaps you could write something, or maybe it is already available in a different mail client. > 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. The easiest form to make a post is unlikely to be the easiest form to read and understand it. On perl.beginners there are two acceptable forms: bottom-posting and interleaved posting. To my knowledge there are no written rules to that effect, but I am sure all regular posters would agree with me. To top-post when you "want to send a final message and [...] don't need any answer" is unforgiveable. The post you have quoted has been written so that it reads fluently from top to bottom. You add something more to the top and, whether or not you need an answer, any subsequent contributor has to replace your entry at the end before his addition. >> 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. As you said where? You didn't even quote your own post that you refer to. You should use a 'certain style' because other people understand it. As I said, there is always a chance that anything we have written will be used in circumstances that we don't expect or imagine. >> The documentation that John referred you to recommends >> >> =begin comment >> : >> =end > > And is this a valid perldoc mark? Yes. John referred to perldoc -q "How can I comment out a large block of perl code" which says: > How can I comment out a large block of perl code? > > You can use embedded POD to discard it. Enclose the blocks you want to > comment out in POD markers. The <=begin> directive marks a section for a > specific formatter. Use the "comment" format, which no formatter should > claim to understand (by policy). Mark the end of the block with <=end>. >> 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? No you haven't been unkind. I was being light-hearted, and it referred back to the paragraph above where I said: > 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. Rob -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
