Re: Reloading Library Files

Ted Prah wrote: > That explains the library files not reloading - Thanks! Great! >>I suppose if you want to use the cheap workaround, you have to >>s/require/do/. Remember that the guide suggests the lib.pl trick as a >>workaround, not a solution you go with during the normal development. > >

Re: Reloading Library Files

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

Re: Reloading Library Files

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 declaration and make the

Re: Reloading Library Files

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 te

Re: Reloading Library Files

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? do you test only this script alone? What happens if you add the package declaration and then call it using the full name? e

Re: Reloading Library Files

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 to see my changes? My > test code and environment is below. Hmm, I haven't used StatINC for a long time, any

Re: Reloading Library Files

Thanks Drew, I tried that, but it did not work. Ted Drew Taylor wrote: > Have you tried moving the PerlInitHandler & PerlSetVar up and out of the > directive, making it global for the server? I'm not sure that > would fix it, but it's worth a try. > > Drew > > At 02:37 PM 5/17/02 -0400, Ted Pr

Re: Reloading Library Files

Have you tried moving the PerlInitHandler & PerlSetVar up and out of the directive, making it global for the server? I'm not sure that would fix it, but it's worth a try. Drew At 02:37 PM 5/17/02 -0400, Ted Prah wrote: >I have tried Apache::Reload as well, but I get the same results. > >Ted >

Re: Reloading Library Files

I have tried Apache::Reload as well, but I get the same results. Ted Drew Taylor wrote: > Take a look at Apache::Reload or Apache::StatINC. Reload is more flexible, > but 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 p

Re: Reloading Library Files

Take a look at Apache::Reload or Apache::StatINC. Reload is more flexible, but 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 Drew At 01:38 PM

Reloading Library Files

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