Hi Rhesa > > Alternatively, we could force lots of CGI.pm globals back to their > > default state in state in the test suite. > > That would be a maintenance hazard. > > I'd probably opt for recommending against hacking up CPAN modules, and to use > the documented ways of customizing behavior. Altering package globals is a > great way to produce unwanted action at a distance, and we all know how evil > that is.
It gets worse. What about people who have deliberately changed globals, and whose code would start to fail if you unilaterally forced those globals back to some (alleged) default value under certain conditions. So, nope, not our problem. -- Ron Savage [EMAIL PROTECTED] http://savage.net.au/index.html ##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################
