in reply to 'Using' modules

I suspect that you have the same function names in different modules. Also, if you're useing or requireing, don't do. In fact, don't ever do.

I have used do in production code to source in files exactly once in my career, and the file that was done had one (large) configuration variable in it. (That hack was removed in a later version.) do skirts too many safeguards, such as the built-in #ifndef mechanism that use and require provide.

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Replies are listed 'Best First'.
Re: Re: 'Using' modules
by hotshot (Prior) on Aug 28, 2003 at 05:35 UTC
    but I can't just do:
    use 'test.pl';

# or
use 'test.ph';

    [download]
    It shouts for syntax error, use argument suppose to be a module name, not a file name, so what else can I do?

    Hotshot
[reply]
[d/l]
[reply]
      Try require, then. Or, rewrite test.pl so that it fits the model for use. (I recommend the latter, simply because it's generally better.)

      ------
      We are the carpenters and bricklayers of the Information Age.

      The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

      Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

[reply]

In Section Seekers of Perl Wisdom