Instead, you're supposed to use use Foo; or require "Foo.pm"; or even do "Foo.pm";. Unfortunately, all of these seem to have side effects and semantics which conflict with one handy use of #include: organizing large flat modules into more manageable chunks.
I tried doing something like the following, but the value of __PACKAGE__ was not 'Mod' inside Mod-part1.pm, as I would have expected. Instead, it was of value 'main'. Thus, all the subs in Mod-part1.pm are added to the wrong namespace.
Mod.pm:
package Mod; use base 'Meta'; ... require "Mod-part1.pm"; require "Mod-part2.pm"; __END__ =pod ... =cut
Mod-part1.pm:
BEGIN { print __PACKAGE__, $/ } sub one { ... }
Mod-part2.pm:
BEGIN { print __PACKAGE__, $/ } sub two { ... }
Of course, this example is minimal; my example module has about six large subs in each of about six parts, all of which must (unfortunately) be in the same module namespace.
If I reassert the package name at the beginning of a part file, it loses all of the other common preparatory code like use base or other modules.
Any ideas on how I can avoid 4000 lines of many module subs in one source file?
--
[ e d @ h a l l e y . c c ]
In reply to organizing large flat modules? use, require, do, ... by halley
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |