Hello MichelleM

My guess is that either you access your undeclared variable before:

        print "content-type: text/html\n\n";
[download]

... or that you have troubles with buffering. Generally error messages are flushed right off and other printing is buffered

This problem would manifest itself in the error log as something line "Premature end of Script Headers "

This may be clearer if you run your script at the command prompt and your warning comes before your header

You can turn off buffering by setting  $|=1

There is a really good nodo on buffering problems: but I can't find it... Suffering from Buffering

update: there is some apache 2.0 buffering discussion here

Actually, in this case, it comes after the headers. And running my script at the command line was how I figured out about the issue of warnings, because I was so puzzled. But thanks for the details on buffering, that comes in handy.

I think the key item in your post is Apache 2.0 - isn't it still a bit buggy? Anyways, warnings such as the one you encountered are trivial and usually more of a burden to fix than they are to ignore. However, i really feel compelled to have warning free code, and instead of turning off strict, i would have gotten rid of the warning like so:

foreach my $record (@records) {
   foreach my $key (keys %$record) {
      my $val = $record->{$key} || '';
      print "$key:$val";
      print $q->br;
   }
}
[download]

I do know that extremely uses Apache 2.0 - he might be of help to you.

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Thanks jeffa, I like this solution to getting rid of the warning - although I have decided for now to just turn warnings off. I don't really have the option on this server to downgrade to 1.3.