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. > > > I didn't realize that using the library wrapper was a cheap workaround > to the nested subroutine problem. The effects of the nested subroutine > problem is my biggest concern with writing code for mod_perl. What > I liked about the lib.pl trick is that it completely eliminates this problem. > I won't lose sleep wondering if somehow the code went into production > with a nested subroutine. I realize that there are other ways to eliminate > the nested subroutine problem, but what are the preferred techniques > used by mod_perl developers? Check the error_log file for problems > and fix as needed? The majority are discussed here: http://perl.apache.org/release/docs/general/perl_reference.html#Remedies_for_Inner_Subroutines Declaring the package in your libs is a good idea. Because if you don't, most likely you are going to encounter this problem: http://perl.apache.org/release/docs/1.0/guide/porting.html#Name_collisions_with_Modules_and_libs The solutions are discussed there as well. > Check the error_log file for problems and fix as needed? Ted, this is not an option, this is a must thing to do. If you don't monitor constantly the error_log file while developing you are looking for a trouble. http://perl.apache.org/release/docs/1.0/guide/debug.html#Warning_and_Errors_Explained __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
