in reply to a simple include....
What's wrong with 'use'? I, and probably most of the perl community, develop common code routines all the time - I typically create a perl 'module' - put my common code in there - and then 'use' that module anytime I need access to that code.
If you're not yet familiar with Perl's 'perldocs', get familiar with them. I just did 'perldoc perl', and then searched(using the forward slash '/') for 'module', and here are a few things I found at the top:
perlmod Perl modules: how they work perlmodlib Perl modules: how to write and use perlmodstyle Perl modules: how to write modules with + style perlmodinstall Perl modules: how to install from CPAN perlnewmod Perl modules: preparing a new module fo +r distribution
So, to read the perldocs for 'perlmod', I'd do 'perldoc perlmod'.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: a simple include....
by pcouderc (Monk) on Apr 30, 2003 at 14:24 UTC | |
by Aristotle (Chancellor) on Apr 30, 2003 at 14:55 UTC |