Stas Bekman wrote:
> Ted Prah wrote:
> > Thanks for the input Stas. I found your debugging methodology
> > to be very informative and especially useful in a mod_perl environment.
> >
> > I tried your suggestion of commenting out
> > require $key;
s you 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 modul
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: text/plain\r\n\r
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
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
StatINC has been around a little longer. Both have worked well for me.
> > > But be sure that you don't use these modules on a production server. :-)
> > >
> > > httpd.conf
> > > ==
> > > PerlInitHandler Apache::Reload
> > >
e 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 libr
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
