Thanks for the replies so far.

Reading, I found

http://perl.apache.org/docs/general/perl_reference/perl_reference.html#use____require____do_____INC_and__INC_Explained

which points out:

First, let's see what are the contents of @INC on my system:
% perl -e 'print join "\n", @INC'
/usr/lib/perl5/site_perl/5.005
.

Notice the . (current directory) is the last directory in the list.
[download]

And I note that in the error message I receive, "." is the last entry. That is, @INC does in fact have the current directory in it. So I think that when I use the correct relative path, "../", it is finding it.

So the mystery is the original "bad name" error.

---

In reply to Re: Bad Name or Missing @INC entry - "require" path fail. by punch_card_don
in thread Bad Name or Missing @INC entry - "require" path fail. by punch_card_don

Title:
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.