Theo E. Schlossnagle wrote:
I have also noticed something like this previously, but that happened with $Request->ServerVariables($name). Calling this function sometimes resulted in a similar error you have experienced.Josh Chamas wrote:This is when an old $Response object is no longer valid. This is normally
caused by my closure or bad scoping issues.
I assumed as much. However, it seems that:
sub AppendToLog { shift->{asp}->Log(...); }
should bde
sub AppendToLog {
my $self = shift;
if($self && $self->{asp}) {
$self->{asp}->Log(...);
}
}
in Response.pm. Why? My $Response variable still exists and as I don't call Log directly it seems that it shouldn't return such a hard error (die) when Apache::ASP makes that call internally.
I can do the later... But not the first. While we run both on almost all our code bases, this particular code base is a legacy one (written by another company) with over 200k lines of client .pm and .asp files. (over 100k of custom perl modules alone). So, retroactively adapting all legacy code to use strict is infeasible.Well, the other thing is that Apache::ASP is mod_perl. You _must_ rewrite "unclean" code if you want to use mod_perl. In general , mod_perl code should be use strict compatible, there is little you can do about that. Probably you should write an Apache::ASP application, and call your modules outside the scope of ASP, if nothing else works.
- Csongor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
