I want to touch on a couple points of footpad's.

While some off-topic (e.g. non-Perl) discussion is tolerated, it's best to limit that as much as possible. Remember, we're here to further our understanding of Perl. If you're in doubt, float the idea via CB (as I presume you did on this one) and see what the response is.

Almost two points to remember on this:

1. OT posts should be labeled as such. I'd like to believe that my (OT) Apache Server issue post demonstrates the finer points of an OT post. It has some relation to what I am doing in Perl, although it is not related to actual Perl code.
2. Responses to OT posts should be limited to helping out with the problem. If you have a problem with an OT post, -- it and be done with it. If you absolutely have to make a point to the author, /msg him/her. Of course, this is just a peeve of mine in relation to the above node.

For example, if you're getting error messages, tell us what they are. Don't just give us a dump, though. Filter through them, find the most relevant ones, and then provide the summary.

footpad forgot the golden rule, even though it's written everywhere: use strict and -w. Update: In case you're throwing out some CGI code, -T is an option that I shouldn't have had to be reminded about. :) Thanks, footpad for keeping me on my toes. End Update

And there are a few things I'd like to add:

• Accept the fact that you aren't the best programmer. This is important if you post code. Your code is going to get reviewed since this is a public forum. People are going to give you pointers on how to do something better. This is not a personal attack. merlyn's been doing this far longer than you have.
• The best thing to do if you find yourself in a flame war is to throw buckets of water into the discussion. Pride is only useful if you wish to be proud of yourself. Piss off the wrong people and that's nothing to be proud of.
• footpad mentions the Search and Super Search. I'm going to mention the Random Node. If you're not here for a particular reason, then go find a reason to be here. I'm not saying that every visit to PM has to have a reason, but that if you're bored and want to learn, this may have some acceptable side effects.
• Make friends with those above and below you. I see more coteries formed in the CB than anywhere else. And it's always nice to know that if you are needing a few points, those people will be willing to help with a level up (your welcome, Lexicon). P.S. the other users is in XP order.

That's just some of my extra thoughts to throw out. ++ to footpad for sharing the secret to his success. :)

ALL HAIL BRAK!!!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.