in reply to CGI inconsistencies
I know, I tried all those things. I have strict, and CGI:Carp for printing errors to browser, and I know what the error for lexically scoped variables looks like. The thing is, my script worked for some time. Then, one day, is suddenly didn't have the value for the variable anymore. The variable was empty, not outside of its scope. The weird thing is that the next day, everything was fine again. To me, this doesn't seem like a problem with my scripts. And no, I don't have access or control over anything my host does. By the way, I looked and the host has the newest version of Perl installed, so...
Until Next Time...
Just Another Perl Wannabe
Re: Re: CGI inconsistencies
by graff (Chancellor) on Apr 08, 2003 at 02:45 UTC
|
I looked and the host has the newest version of Perl installed, so...
So, the script is working now (after not working for a day) without ever being modified? Does the variable's value depend on input from the cgi form? Are you worrying that it might happen again? Were you hoping we could provide some answers, or just venting about something that seems inexplicable? (Is this too many questions, and we should just drop it?)
It could be interesting to know when this newest version of perl was installed on that server -- you could run "perl -V" in backticks and print the line that says "Compiled at ..."; indeed, print all the output, because there are many relevant facts provided there (e.g. whether your notion of "newest version" matches someone else's), and unless you provide at least some details of that sort, it's kind of pointless to give the appearance of asking for help. | [reply] |
|
Well, mainly because, 1., I wanted an explanation as to the inconsistencies, and 2., Yes, I am afraid it's going to happen again, and would like to know how to fix it (or at least how to avoid it. Until next time...
Just Another Perl Wannabe
| [reply] |
|