I am not subscribed to the list, so please copy me on any replies.
We have recently upgraded to the latest 1.3.x apache and mod_perl
and our code is flagging a warning that it did not before.
I am hoping it is the result of a bug fixed in Apache or mod_perl
and that I can change our code to
Ah, this was a while ago,
I did actually trace the problem down. The handler was returning undef
which was causing these warnings. It was just not taht obvious from the
warning given.
Graham.
On Thu, Jun 14, 2001 at 09:48:42AM -0700, Doug MacEachern wrote:
On Wed, 7 Mar 2001, Graham Barr
Does anyone have any idea what could be causing
Use of uninitialized value at PerlHandler subroutine `VC::Delivery::Cycle::handler'
line 1.
to appear in the errorlog ?
I even added
local $SIG{__WARN__} = sub { warn "here" };
as the first line of VC::Delivery::Cycle::handler, but it never
On Thu, Mar 30, 2000 at 04:07:38PM -0500, Geoffrey Young wrote:
Hey, I'm not trying to redo anyone's work or step on toes...
I am sure your not, but on the other hand when two modules are so
close in functionality it can help to merge them. There are
several reasons why this can be benificial,
