dave_apache_asp wrote: > > I had already made sure this wasn't a browser-caching issue with a > random number display; it is definitely server-side. Per Joshua's > suggestion, I took the subroutine out of the ASP and that seems to > have solved the problem. Apparently subroutines compiled in ASPs > retain their original variables? >
subroutines that have variables they are using that are improperly scoped will be retained in subsequent requests. Improper scoping of variables can result in my closure behavior. As long as all variables in a subroutine are accessing global variables ( like $main::Response ) or my() scoped variables, then that subroutine should be able to be written in a ASP script fine. Moving subs to a real perl module/package avoids these problems by forcing variables to be properly scoped during compilation. 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]
