BrowserUK is exactly right. The foreach() loop asks for a list. The <> diamond operator behaves differently in list context than it does in scalar context. In scalar context, each time the diamond operator is evaluated it hands you the next line of the file. In list context, the entire file is slurped into memory at once and a list is created (and enumerated for the foreach loop).
The $. special variable tells you what line of a file you most recently read. The foreach loop only evaluates the <> operator one time -- when it slurps in the entire file. Each time through the loop the foreach operator hands you the next line of the list, but the entire file has already been read into memory, and the $. variable tells you this by telling you that you're on line 4.
This is a valuable lesson on how to quietly build a piece of code that cannot scale well when file sizes grow. If it weren't for the fact that the $. variable did something you didn't anticipate, you might have left the foreach loop in your code. Then one day when the file is 2GB huge, your client would call and ask why the program is locking up his system.
Sticking to the while() construct will eliminate that issue.
Dave
In reply to Re^2: Line number problem with foreach
by davido
in thread Line number problem with foreach
by vinoth.ree
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |