As best as I can tell this is actually a file named "Bar.pm" in a subdirectory named "Foo".
Same thing. The directory is considered to be part of the filename, really, as the distinction is often meaningless in practice, and files' actual names cannot contain forward slashes anyway, so there's no ambiguity.
Can this sort of thing go on to multiple levels? Like, could we have a module named "Utterly::Completely::Foo::Barred::Up" that would be defined in the "Up.pm" file located in the "Utterly/Completely/Foo/Barred" subdirectory (of a member of @INC, I guess)?
Yes. To give a random example from my system, App::Prove::State::Result::Test lives in a file named Test.pm in a (sub)directory called App/Prove/State/Result.
And, is that the only place where such a module could be found, or could it also be in a file of a different name and/or in a different subdirectory?
Yes, that's the only place where such a module could be found, though @INC may of course contain several places where Perl will look.
-
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.
|
