Thank you for all the responses so far. I'm tied up for a few hours and will probably not get back to it until tonight.

I don't want to ruffle any feathers more than I already have but in Perl there is a pretty big jump going from beginner to intermediate skill levels. All the various ways of doing things, different methods, different packages, etc. can be overwhelming to someone who doesn't yet have the intermediate/advanced insight into the inner workings of Perl. It is easy to look at a variety of books and postings and feel like they all go in different directions and are inconsistent with each other. In some cases this is true, in some cases it isn't. But we beginners can look at the various methods and various shortcuts and end up going around and around in pointless circles until we are too burned out to see what is in front of our face. I think of myself as a Perl advanced beginner. I have been around Perl for years, but only writing a couple of small programs a year I have never made that jump up to having better insight into the inner workings of Perl.

I try not to post code unless it is as clean, short and to the point as possible. If I am going to ask someone to take their time to look at my code I try not to waste their time. I also know that once I have posted some garbage code to the thread I have probably killed the possibility of people taking the time to read any code that might follow it. I ran out of time last night and didn't have another batch of clean code to post.

One of the great things about Perl is that there are many ways to do things and many shortcuts available to make coding easier for those with knowledge and skill. One of the bad things about Perl is that there are many ways to do things and many shortcuts that make understanding difficult for those with limited Perl knowledge and skill.

Beginners can struggle for a long time with two different tutorials that have details that look very different (to the beginner). There are times when after hours of work and Googling a beginner finds out that something from one source is only good for Perl X.X and below where something from another source is only good for Perl Z.Z and above. We can spend hours only to find out that it was common knowledge within the Monk community that we were barking up the wrong tree.

The questions from us beginners reflect that we do not yet have the knowledge and insight of intermediate/advanced Monks. Some days no matter how many times Grasshopper grabs for the pebble we still come up empty handed.

In reply to Re: File upload under Apache2 by Bruce32903
in thread File upload under Apache2 by Bruce32903

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.