Using home-grown modules in mod-perl

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

From: Kent, Mr. John \(Contractor\)
Subject: Using home-grown modules in mod-perl
Date: 15:55 on 31 Jan 2005
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=20

will it work to NOT use EXPORT and say in the startup

/use/lib qw (/users/webuser/homegrown/lib);
use MyModule();


In other words must I specifically export sub-routines and bring them =
all into the name space
for mod-perl to compile them into Apache?

Thank you,
John Kent
Webmaster
Naval Research Laboratory
Monterey, CA
http://www.nrlmry.navy.mil/sat_products.html

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
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