might have.
Your code to work around Exporter worked fine. However,
I think I'll stick with using Exporter so that I can make use
of the export tags.
Thanks again!
Ted
Stas Bekman wrote:
Ted Prah wrote:
Hi again,
I'm having trouble seeing module changes when I reload
a script that uses
Hi again,
I'm having trouble seeing module changes when I reload
a script that uses it. I'm using Apache::Reload and my test
script/module is as follows:
test.pl
#!/usr/local/bin/perl
use strict;
use warnings;
use My::Test qw(:subs);
print Content-type:
Stas Bekman wrote:
Ted Prah wrote:
Thanks Drew, I tried that, but it did not work.
What happends if you add:
PerlWarn On
in httpd.conf
or
start the script with perl -w?
any warnings?
I had PerlWarn On and added -w anyway, but there were no errors.
do you test only
Stas Bekman wrote:
Ted Prah wrote:
do you test only this script alone? What happens if you add the package
declaration and then call it using the full name? e.g.:
Yes, this is the only script (and corresponding library file) that I use
for this test. When I use the package
Hi,
I am new to mod_perl and am having problems seeing the
changes made to library files. Must I restart the server every
time I change a library file in order to see my changes? My
test code and environment is below.
z.pl - test script which calls entry_point in z_lib.pl
on a production server. :-)
httpd.conf
==
PerlInitHandler Apache::Reload
Drew
At 01:38 PM 5/17/02 -0400, Ted Prah wrote:
Hi,
I am new to mod_perl and am having problems seeing the
changes made to library files. Must I restart the server every
time I change a library file in order
these modules on a production server. :-)
httpd.conf
==
PerlInitHandler Apache::Reload
Drew
At 01:38 PM 5/17/02 -0400, Ted Prah wrote:
Hi,
I am new to mod_perl and am having problems seeing the
changes made to library files. Must I restart the server every
