The problem is that while does not iterate over a list, it simply checks for a true value. For example, while (1){} will run forever, whereas for (1){} will run once.

The same behaviour occurs when test being evaluated is param(). Additionally, while (param()){} will not modify $_. Perhaps you tested the script without any arguments, in which case it would have behaved as expected.

Here is a simple test: 

#!/usr/bin/perl
use strict;
use warnings;

use CGI qw(param);
my $runs =0;
my @num;

print "Content-type: text/plain\n\n";

while(param()) {
    printf "run %d\n", $runs++;
    if ($runs > 10) {
        print "Ran over 10 times\n";
        exit;
    }
}

[download]
You can verify it by adding the parameters on the commandline, e.g. 
perl foo.pl a=b

[download]

In reply to Re^4: how to pull in all params that are numbered by imp
in thread how to pull in all params that are numbered by Anonymous Monk

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.