Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I'm happy for MS OSes to be bashed. They need it. I'm also more than happy to bow down to Unix users. The ones I've met here have been very helpful.

I draw the line at bashing windows users. Often they come to perl with no background in unix, c or even no programing experience at all. The learning curve is obviously steeper ('the command prompt?').

I've just installed my first module from CPAN (I couldn't find it with ppm). If it wasn't for the marvellous tachyon (again, many thanks) patiently holding my hand as I painfully stumbled my way through I would never have done it. node_id=378614 (I've just looked at it again and I want to weep!)

I welcome giricredwolf's tutorial, it will help me and many others.

...and I nearly forgot my excuse, I'm addicted to pinball!

In reply to Re^3: Tutorials Suggestion by wfsp
in thread Tutorials Suggestion by giricredwolf

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.