Greetings,
I have some home-grown modules that I wish to have pre-compiled into a heavy
Apache server
via mod-perl.
Must my module EXPORT the desired sub routines, and must the startup.pl file
say
/use/lib qw (/users/webuser/homegrown/lib);
use MyModule;
OR
will it work to NOT use EXPORT and
On Jan 31, 2005, at 10:55 AM, Kent, Mr. John ((Contractor)) wrote:
will it work to NOT use EXPORT and say in the startup
/use/lib qw (/users/webuser/homegrown/lib);
use MyModule();
That's what I do.
Jonathan Vanasco wrote:
On Jan 31, 2005, at 10:55 AM, Kent, Mr. John ((Contractor)) wrote:
will it work to NOT use EXPORT and say in the startup
/use/lib qw (/users/webuser/homegrown/lib);
use MyModule();
That's what I do.
Does your module work with a blessed references, or it a module
containin
Re: Using home-grown modules in mod-perl
Jonathan Vanasco wrote:
> On Jan 31, 2005, at 10:55 AM, Kent, Mr. John ((Contractor)) wrote:
>
>> will it work to NOT use EXPORT and say in the startup
>>
>> /use/lib qw (/users/webuser/homegrown/lib);
>> use MyModule();
-- "Kent, Mr. John \\(Contractor\\)" <[EMAIL PROTECTED]>
Leo,
I am not using OO coded modules. My modules
contain methods.
Other routines call this module's routines as you indicated:
In order to solve other mod-perl problems I followed Stas's recommendation
to call all my routines thusly:
MyMod
Kent, Mr. John (Contractor) wrote:
Leo,
I am not using OO coded modules. My modules
contain methods.
Other routines call this module's routines as you indicated:
In order to solve other mod-perl problems I followed Stas's recommendation
to call all my routines thusly:
MyModule::foo(...)
So, sin
Kent, Mr. John (Contractor) wrote:
Greetings,
I have some home-grown modules that I wish to have pre-compiled into a heavy
Apache server
via mod-perl.
Must my module EXPORT the desired sub routines, and must the startup.pl file
say
/use/lib qw (/users/webuser/homegrown/lib);
use MyModule;
OR
wil
