comment on

I think that the confusion here is that inclusion of a file is generally tied closely to the specification of a separate package namespace. This is a good idea (to avoid collisions between variable and subroutine names), but isn't really required. Consider program foo.pl:

#!/usr/bin/perl -w

use strict;

use lib '.';
use Inc1;
use Inc2;

print "Here we go!\n";
foo1();
foo2();
print "All done.\n";
[download]

If modules Inc1.pm is specified as:

# first include file
sub foo1
{
   print( "This is a test from foo1.\n" );
}

1;
[download]

and Inc2.pm is:

# second include file
sub foo2
{
   print( "This is a test from foo2.\n" );
}

1;
[download]

You get the expected results -- that subroutines foo1 and foo2 are called from their corresponding modules.

Unlike (for example) Pascal, the Perl programmer is not burdened with the arbitrary preferences of the person who specified the language. TMTOWTDI. This is not merely a slogan, it's a language reality, and you have hereby been provided with more than enough rope to hang yourself. Use it in good health.

In reply to Re: Multiple Files, One Script Possible? by papidave
in thread Multiple Files, One Script Possible? by Anonymous Monk

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.


Think about Loose Coupling
	PerlMonks