in reply to Multiple Files, One Script Possible?

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

#!/usr/bin/perl -w use strict; use lib '.'; use Inc1; use Inc2; print "Here we go!\n"; foo1(); foo2(); print "All done.\n";

If modules is specified as:

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

and is:

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

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.