Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Unexpected CGI param behavior

by pc88mxer (Vicar)
on Jun 24, 2008 at 00:47 UTC ( #693640=note: print w/ replies, xml ) Need Help??

in reply to Unexpected CGI param behavior

I think CGI implements this behavior so that param() can support both scalar and list context. In list context it returns all the values for a parameter and in scalar context it just returns the first value.

If it returned undef for unknown parameters, then this wouldn't work:

my @vals = $q->param('...'); print Dumper(\@vals); # would print [ undef ] not [ ]
That is, @vals would not be the empty list but a list containing undef.

A work-around is to use scalar:

my $var = { first => scalar $q->param('first'), second => scalar $q->param('second'), };

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://693640]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2016-08-28 17:12 GMT
Find Nodes?
    Voting Booth?
    The best thing I ever won in a lottery was:

    Results (394 votes). Check out past polls.