Two more wonderful notes.

Sporty, you're right. I will add more ex(ample|planation) in the next version. I also think this will increase the pleasure people will find when reading the article.

BrowserUk, yes, I agree with you. It's better not to tell what others SHOULD do or SHOULD NOT do, but that makes a less interesting text in my opinion.
But, as I already said, I will add examples in the next version.

Thank you for the useful comments and critics, and for the time you spent to help me.

I still welcome more comments.
Especially, I want to remention my wish to fill in the module and link gaps. I do know I can't expect you to do my work (for it is my work) but I would really like to see that someone finds the modules and pages I'd like to refer to.
Within a couple of weeks, I will be able to do that myself but for now I am stuck with a expensive dial-up connection (the phone company charges the phone ticks :( ).

Furthermore, I'd like to mention your names in a "word of thanks" chapter. By default, I assume you don't have problems with that but if you do, please let me know.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.