You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by "Randal L. Schwartz" <me...@stonehenge.com> on 2000/05/25 15:29:45 UTC

CGI.pm broken with Apache/mod_perl/warnings? (was Re: XHTML_DTD redefined?)

>>>>> "Perrin" == Perrin Harkins <pe...@primenet.com> writes:

Perrin> "Randal L. Schwartz" wrote:
>> 
>> I'm getting this on every startup:
>> 
>> Constant subroutine XHTML_DTD redefined at /usr/lib/perl5/5.00503/constant.pm line 175.
>> 
>> what's this about?

Perrin> That would be the mandatory warning for redefined inlined subroutines. 
Perrin> That particular one looks like it comes from CGI.pm.  You can make this
Perrin> stop by using Apache::Symbol.

Yeah, it's CGI.pm alright.  So do I complain to Lincoln to fix it, or
is it just a synergy thing between mod_perl, Apache, and CGI.pm that I'll
have to live with?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<me...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Re: CGI.pm broken with Apache/mod_perl/warnings? (was Re: XHTML_DTD redefined?)

Posted by Perrin Harkins <pe...@primenet.com>.
On 25 May 2000, Randal L. Schwartz wrote:
> I got no "no warnings".  this is still 5.5.3 :)

There's always the time-honored

{
  local $^W;
}

- Perrin


Re: CGI.pm broken with Apache/mod_perl/warnings? (was Re: XHTML_DTD redefined?)

Posted by "Randal L. Schwartz" <me...@stonehenge.com>.
>>>>> "Doug" == Doug MacEachern <do...@covalent.net> writes:

Doug> On 25 May 2000, Randal L. Schwartz wrote:
>> Yeah, it's CGI.pm alright.  So do I complain to Lincoln to fix it, or
>> is it just a synergy thing between mod_perl, Apache, and CGI.pm that I'll
>> have to live with?

Doug> are you re-loading CGI.pm?  that's the only way this warning can be
Doug> triggered, from what i can see.  in which case, this wouldn't be a bug in
Doug> CGI.pm, the re-loader simply needs:
Doug> {
Doug>     no warnings;
Doug> }

I got no "no warnings".  this is still 5.5.3 :)

And I'm not doing the reloading, unless this would do it:

in conf:

    PerlRequire mason-startup.pl

in mason-startup.pl:

    package HTML::Mason::Commands;
    ## use CGI qw(-compile :all);
    use CGI qw(:all);

By the way, when I added -compile, it broke on a recent release of
CGI.pm.  Grr.  This stuff seems to be more and more fragile. :)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<me...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

Re: CGI.pm broken with Apache/mod_perl/warnings? (was Re: XHTML_DTD redefined?)

Posted by Doug MacEachern <do...@covalent.net>.
On 25 May 2000, Randal L. Schwartz wrote:
 
> Yeah, it's CGI.pm alright.  So do I complain to Lincoln to fix it, or
> is it just a synergy thing between mod_perl, Apache, and CGI.pm that I'll
> have to live with?

are you re-loading CGI.pm?  that's the only way this warning can be
triggered, from what i can see.  in which case, this wouldn't be a bug in
CGI.pm, the re-loader simply needs:
{
    no warnings;
}