It is not a standard perl error message. I went through mod_perl doc at
http://perl.apache.org/docs/general/perl_reference/perl_reference.html#T
racing_Warnings_Reports
and understand that, the error message appear if one fails to pass a
value to a subroutine before using. Looking through my
Oh yes I did. I always try my script on the command line to ensure the
syntax are ok before running them on the web server with mod_perl. So
the error has to do with mod_perl. Perhaps you may want to take a look
of some examples:
I have a file (output_tab.pm) that I use to generate tables
B. Fongo wrote:
Script_name.pl: Use of uninitialized value in concatenation (.) or
string at output_tab.pm line 42.
Perrin replied:
This is a standard perl error message. It is not related to mod_perl.
You can look in the perldiag man page for a more complete explanation.
B. Fongo wrote:
Did u check what's in line # 42 ? If u run the same
script with same params as stand-alone, do u see the
warning ?
Sreeji
--- B. Fongo [EMAIL PROTECTED] wrote: It is not a
standard perl error message. I went
through mod_perl doc at
Am Sat, 23 Aug 2003 09:48:05 + schrieb B. Fongo:
foreach (@table_data)
{
print qq(td bgcolor='#d0d0d0'$_/td); # Here is line 42
}
as Frank already pointed out, your trouble is the uninitialized $_ value
you have in line 42 (which is exactly what
-CUT--
my $val=$_||'NULL'; print qq(td DEFANGED_bgcolor=0#d0d0d0$val/td);
-CUT--
This is not a very good solution. You would also catch the case where $_
is 0, which may should not happen. You would better do
foreach (@table_data) {
$_ = defined $_ ? $_ : NULL;
On Sat, Aug 23, 2003 at 01:55:03PM +0200, Marcel Greter wrote:
This is not a very good solution. You would also catch the case where $_
is 0, which may should not happen. You would better do
Yes... I always fall into that pithole. I think this is because I find
the 'defined(...) ? ... : ...'
Some small things that needed to be updated. The end user
of version 1.1 wouldn't realize a big change in the behavior.
Although I strongly recommend to install the version 1.2, as
it provides a lot of little corrections, not only in
functionality, but also in display and design.
I have to admit,
Frank Maas wrote:
On Sat, Aug 23, 2003 at 01:55:03PM +0200, Marcel Greter wrote:
This is not a very good solution. You would also catch the case where $_
is 0, which may should not happen. You would better do
Yes... I always fall into that pithole. I think this is because I find
the
OK Guys!
Thanks for all the contributions. All along, I thought mod_perl was
complaining that $_ isn't initialized. Most of the suggestions I got
points to the array (@table_data) in the loop. It is actually true that
the some of the values of the array are NULL.
Thanks again for all those
10 matches
Mail list logo
