The scariest part is Reading The Wrong Manual. Unfortunately there are a lot of bad Perl books out there - most of them quick throwaway CGI focused (if you can actually call them focused) scraps of paper waste that deserve not the effort to put an ISBN number on them.

I accidently wandered into using perl after a few years of being a cold fusion/java on Macintosh programmer - hosting on an NT server I could barely maintain. I was forced to learn perl because clients keep wanting to put scripts from an unmentionable script archive on my server.

Talk about culture shock!

It was like bumbling through the dark and falling off the pier. Picking up a ton of rotten books on perl was like hitting the rocks below and missing the water entirely.

A kind soul gave me learning perl.

Since then I have pretty much stuck to the oreilly books, even went as far as to purchase and run the oreilly webserver on my NT box ( cannot say enough nice things about oreilly - the two thick books for their webserver are overly complete and would be excellent reading for anyone working on the net - even if they *don't* run that webserver).

That said, I still have problems reading through the perldocs - they are written from a perspective I only partially gained relatively recently. Personally I think the most frustrating bits of documentation are sprintf and printf. They basically say - they work like sprintf(3) and printf(3) or some such verbage. I still mess them up constantly. I'm sure many of the monks here chuckle at that and I will someday myself, but it was frustrating trying to learn perl without access to a command line.

So now I am reading the right manuals...I just cannot find the preface and forword so I can understand them properly.

Thanks,

EEjack

In reply to Re: Perl Enlightenment and Personal Journey To It by eejack
in thread Perl Enlightenment and Personal Journey To It by WebHick

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


  • 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! —
  • 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:
    & &amp;
    < &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.