in reply to CGI::start_html and mod_perl

A warning is just what is says. It is warning you about a potential problem with your code. Now you could just suppress it and hope that it's not warning you about a serious error[1]. Or you could investigate it and put right whatever is causing the error.

In this case you're probably using a variable that you haven't put any data into. Fixing the problem might well be as easy as initialising the variable with an empty string.

[1] And if you want to do that then perllexwarn will show you how.

--
<http://dave.org.uk>

"The first rule of Perl club is you do not talk about Perl club."
-- Chip Salzenberg

Replies are listed 'Best First'.
Re^2: CGI::start_html and mod_perl
by Anonymous Monk on Jul 06, 2006 at 23:53 UTC
    I love you guys. I really did mean "warning" rather than "error", sorry about that. My use of warnings is religious so I know what causes them too. I tried the common methods of turning them off in the block where start_html occurs but that didn't work. There were no empty variables since start_html was called with a few hard coded parameters. This occured under the PerlRun handler in the initial phases of porting old code to Registry and handlers. One aspect of our procedure replaces CGI with Apache::Request so we'll remove CGI HTML routines to solve this problem.

    Just wondering if anyone knew about this because it took some time to find the problem and the source was so unexpected.

[reply]

In Section Seekers of Perl Wisdom