Re: Different behaviors between "while" and "map"

[friedo]

The reason this happens is because the while loop is designed to operate on <> like an iterator. Thus, it reads one line at a time until it can't read anymore.

By contrast, using <> as the list for your map block reads the entire file in all at once, incrementing $. along the way. The entire file then gets passed to your map block as one big list, and by this time, $. has already been incremented to the number of the last line, so the same $. gets printed each time through the map block.

[Joost]

Just to expand a little on this: map, grep, foreach and most while constructs all work on perl's concept of lists.

while (<SOME_FILE_HANDLE>)

is special. it does not act like any other iteration construct, not even like any other while() construct. It explicitly iterates over each record ("line") one by one instead of converting the whole file to a list first.

[betterworld]

It helps to know that the loop is expanded to:

while ($_ = <SOME_FILE_HANDLE>){
   ...
}

This shows that <...> is nothing more than a loop condition: the loop body is executed immediately after each evaluation of the <...> operator. This is how a while loop works.

[JavaFan]

Not for the last 12 years or so. It's expanded to

while (defined ($_ = <SOME_FILE_HANDLE>)) {
    ...
}