This worked exactly as intended on my development station, but when I moved it to the production server, Dr. Watson would trigger and halt execution of my script when this line was reached. I checked the server error log for details (as always, I have warnings, strict, and CGI::Carp enabled) to find none. I executed the script from the command line to again find no errors or warnings. I took a look through the script before this line again and verified that $subdivision, $legal and $legal_temp were all defined prior to this line.$legal_temp = $subdivision . "<BR>\n" . $legal;
I was able to work around Dr. Watson by changing the line to read this:
I'm not sure why this works, but it does. And not knowing why annoys me to no end :P$legal_temp = $subdivision . "<BR>\n"; $legal_temp .= $legal;
I have a similar situation with the following line:
No warnings or errors, and all variables are defined prior to use. However, this line also triggers Dr. Watson. By changing it to this:$bodytext .= "<TR><TD align=\"left\">" . ($lcount > 0 ? "<HR>" : "") . + "<FONT size=\"2\">";
the Dr. will leave me alone.$bodytext .= "<TR><TD align=\"left\"><FONT size=\"2\">";
Is there something obvious that I'm doing wrong here? Or is there a difference in how ActivePerl behaves on Win2k as opposed to NT4? I'm confused. . . . if someone can help/explain, it would be greatly appreciated.
Thanks!
MrCromeDome
In reply to Dr. Watson paid my perl script a visit. . . by MrCromeDome
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |