You're right when you suspect that this is too vague to be answered. You show us the lines where you get the unitialized values ($buffer and %FORM), but you don't show us the context of those lines or how the values get assigned.
The lines that you do list appear to be from a hand-rolled alternative to CGI.pm. I could be wrong about that, but I've seen them soooooo many times. Both lines have bugs in them irrespective of the unitiliazed value. The @pairs line ignores that some user agents use a semi-colon to delimit name/value pairs and this is expected to be the standard in the future. The %FORM line suggests that you are using whitespace to delimit multiple form values with the same name. Of course, if one of the form values has embedded whitespace, you can't tell how many values there were supposed to be.
In other words, use CGI or die; -- no offense. If you show us a bit more of your code, we can show you how to convert it to CGI.pm.
Cheers,
Ovid
Vote for paco!
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.
In reply to (Ovid) Re: uninitialized values for arrays suddenly appear
by Ovid
in thread uninitialized values for arrays suddenly appear
by jerrygarciuh
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |