Gary Hawkins wrote:
>
> > > That being said, you should never, never try to parse CGI form
> > data by hand.
>
> What do you use John.
You are attributing a statement to me that was actually written by
Curtis Poe.
John
--
use Perl;
program
fulfillment
--
To unsubscribe, e-mail: [EMAIL PROT
On Dec 19, Gary Hawkins said:
>> > That being said, you should never, never try to parse CGI form
>> data by hand.
>
>What do you use John.
If not the *standard* CGI.pm module, use one of the kid-testing,
mother-approved CGI::* modules on CPAN, like CGI_Lite (or CGI::Lite).
--
Jeff "japhy"
> > That being said, you should never, never try to parse CGI form
> data by hand.
What do you use John.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Curtis Poe wrote:
>
> There are a number of problems with your code snippet, but syntax is not one of
>them. If it is
> indented properly to show scope, you can quickly see that the curly brackets are
>fine:
>
> sub Parse
> {
> my $buffer;
> if($ENV{REQUEST_METHOD}eq'GET')
> {
>
--- Curtis Poe <[EMAIL PROTECTED]> wrote:
> 7. You should be using strict (not everyone does, but code like this tells me the
>programmer
> needs it).
Aack! I rereading the code, I saw that the code is strict compliant and the
programmer may very
well be using that. The last item was kind of
--- Chris Zampese <[EMAIL PROTECTED]> wrote:
> When I execute the folowing script (to insert form input into $In), I get an error
>message
> saying
>
> unmatched right curly bracket line 60 at end of line
> syntax error near "}" Line 60
>
> But I have been through the code over and ove
