Re: Using home-grown modules in mod-perl

[prev] [thread] [next] [Date index for 2005/01/31]

From: Leo
Subject: Re: Using home-grown modules in mod-perl
Date: 16:36 on 31 Jan 2005
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 
containing methods?

The above declaration is for OO coded modules that utilize blessed 
references.

If your module doesn't use blessed references you should try using Exporter.

Exporter pollutes the module namespace a bit so maybe it isn't such a 
purist thing to use but the alternative is to call a method explicitly 
like: MyModule::foo(...)

    perldoc Exporter

Leo

Using home-grown modules in mod-perl
Kent, Mr. John \(Contractor\) 15:55 on 31 Jan 2005

Re: Using home-grown modules in mod-perl
Jonathan Vanasco 16:09 on 31 Jan 2005

Re: Using home-grown modules in mod-perl
Leo 16:36 on 31 Jan 2005

RE: Using home-grown modules in mod-perl
Kent, Mr. John \(Contractor\) 17:15 on 31 Jan 2005

RE: Using home-grown modules in mod-perl
Steven Lembark 17:20 on 31 Jan 2005

Generated at 12:39 on 05 Feb 2005 by mariachi v0.52