This is rather frustrating. I put a lot of energy into becoming a competent Perl programmer, I tell you a lot of valuable information point blank, and you just ignore it all?

Sure, you have lots of croak calls. But if your code is like any half-way sane person's, none of them are expected to be called in regular use. Now based on what happened when you did call it, I am willing to bet that your installation is messed up.

I am telling you that based on quite a bit of experience. Please do not disregard that statement. If it is true, then all of your error handling is going to be giving you back useless error messages. If you are a good programmer, that statement should bother you. A lot.

Furthermore compare the error with what your code tries to put out. Your error reporting doesn't actually give the error it is supposed to. That is worrisome. However even if your code worked as you expect, the error message that you would have gotten would be wrong and misleading. That underscores my point that I made before about error handling, which you seem to be ignoring. But a good programmer wouldn't ignore that. A good programmer should be bothered if error handling gives you messages that send you down a blind alley. A good programmer doesn't want to make debugging harder.

So I am telling you the following.

  1. I think you are dismissing my belief that your installation has problems far too easily.
  2. The fact that there is no connection between what the error was and what the message is that you got should be a giant red flag that should worry you.
  3. Your error handling is broken and needs fixing. Even if you got the message that you had worked to put there, the result would have just left you confused again. If you take the suggestions that I gave you earlier, this would not happen again.
  4. Your motto is, typos and all, "Wierd things happen, get used to it". Well that attitude is extremely dangerous in a programer. Yes, weird stuff happens. But you shouldn't just learn to live with it. Instead you should be bothered by it, investigate it, and make it so it doesn't happen any more.
Well if I wasn't sick as a dog, I probably would rewrite this to come off in a kinder way. But I am, and I think that what I am saying has value. So please ignore the tone if you need to and focus on the message...

In reply to Re (tilly) 3: New Problem? by tilly
in thread require $package? by Flame

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.