Question from the perlmod man pages.



I'm sort of drawing a stump on the following:

"Perl packages may be nested inside other package names, so we can have
package names containing ::. But if we used that package name directly
as a filename it would make for unwieldy or impossible filenames on
some systems. Therefore, if a module's name is, say, Text::Soundex,
then its definition is actually found in the library file
Text/Soundex.pm."

Say I have a module name Text::Soundex. I use this in my Perl script
as:

use Text::Soundex;

I know there is a module called Soundex.pm. I also know there is a
directory
name with the name Text. However, would there also be a module named
Text.pm?

Chad

.



Relevant Pages

  • Re: Question from the perlmod man pages.
    ... "Perl packages may be nested inside other package names, ... as a filename it would make for unwieldy or impossible filenames on ... and does not establish a hierarchical relationship ...
    (comp.lang.perl.misc)
  • lxr-cvs woes
    ... I am trying to get lxr-cvs running under apache2 ... I think the package needs several perl packages that are not in its ... dependencies. ...
    (Debian-User)
  • Re: [Sid] perl breaks apache
    ... | access to those versions of Perl packages but I can't quite figure out ... | versions and install the 5.8.3-3 versions. ... In aptitude, '+' selects a package for installation. ... navigate through the package list to the package. ...
    (Debian-User)
  • Re: Question from the perlmod man pages.
    ... Jim Gibson wrote: ... "Perl packages may be nested inside other package names, ... as a filename it would make for unwieldy or impossible filenames on ...
    (comp.lang.perl.misc)