Josh: I always have UseStrict on, but your suggestion of turning on PerlWarn was like some cold water in the face. I normally have it turned on, but not this time. That simple step illuminated a number of silly little issues that conspired to put my application in the crapper. While it's still not perfect, I am back on track adding value and not time.
Sometimes it's real nice to have someone looking over your shoulder, thank you. Also, as you probably suspected, this problem was apparently related to my other post RE: strange error, it has become remarkably better. Thanks again. Steve > -----Original Message----- > From: Josh Chamas [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, September 17, 2002 2:36 AM > To: Stephen Bardsley > Cc: Apache::ASP Mailing List > Subject: Re: dynamic module > > > Stephen Bardsley wrote: > > I'm still open for suggestions on what might cause a > > global to be unreliable in subs or other .asp > > scripts. Thanks again. > > > > I recently discovered a combination of UseStrict setting > with PerlWarn On can uncover some nasty errors like > my closure variable scoping issues, that could be getting > mistaken for globals & such. You might give those configs > a try and see if anything breaks. > > Regards, > > Josh > ________________________________________________________________ > Josh Chamas, Founder phone:925-552-0128 > Chamas Enterprises Inc. http://www.chamas.com > NodeWorks Link Checking http://www.nodeworks.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
