|Think about Loose Coupling|
Re: Bad Name or Missing @INC entry - "require" path fail.by punch_card_don (Curate)
|on Feb 26, 2013 at 07:30 UTC||Need Help??|
Thanks for the replies so far.
Reading, I found
which points out:
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.
Time flies like an arrow. Fruit flies like a banana.