In the penultimate paragraph of p.109 about the foreach statement it
is stated that it must be typed on a single line when entered on the
command line. That is incorrect.
Andrew Watt MVP
In the penultimate paragraph of p.109 about the foreach statement it
is stated that it must be typed on a single line when entered on the
command line. That is incorrect.
Andrew Watt MVP
good catch - it used to be that way, but we fixed it!
jim
--
James W. Truher [MSFT]
Windows PowerShell Program Management
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew Watt [MVP]" <SVGDeveloper@aol.com> wrote in message
news:3nj172l73kb68elpf31o2au4fa8626iq31@4ax.com...
> In the penultimate paragraph of p.109 about the foreach statement it
> is stated that it must be typed on a single line when entered on the
> command line. That is incorrect.
>
> Andrew Watt MVP
| Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| break from foreach statement | Kobus Klue | PowerShell | 4 | 08 Oct 2007 |
| foreach, foreach-object & begin/process/end scriptblock clauses... | Clint Bergman | PowerShell | 12 | 16 May 2007 |
| Re: Empty output oddity in conjunction with foreach statement | Jacques Barathon [MS] | PowerShell | 1 | 28 Mar 2007 |
| Re: Empty output oddity in conjunction with foreach statement | Rob Campbell | PowerShell | 0 | 27 Mar 2007 |
| possible bug with using the $foreach keyword inside foreach loops.. | klumsy@gmail.com | PowerShell | 6 | 16 Nov 2006 |