Yes. param is context sensitive. In a scalar context, it returns a single scalar value of the first (arbitrary order) param with that name, or undef showing that nothing has that name. In a list context, it returns a list of all params with that name, which could indeed be an empty list, as you saw.

You are using a list context, and using the result in a list, so an empty list disappears. Had there been multiple elements, you'd be messed up the other way, in that your later parameters would have been pushed out of place the other way.

I'd rewrite that code as: 

makeMenuInput(scalar $query->param('category'), scalar $query->param('
+subcategory'),"allon");

[download]

-- Randal L. Schwartz, Perl hacker

In reply to Re: Unexpected behavior after passing $query-param('bar') as subroutine parameter by merlyn
in thread Unexpected behavior after passing $query-param('bar') as subroutine parameter by Banky

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.