Re: [PSH] Methods/functions and blank spaces
- From: "/\\/\\o\\/\\/" <no@xxxxxxxx>
- Date: Sat, 29 Apr 2006 13:39:32 +0200
Careful there. I can't do this:
ri a.txt b.txt
is this example I guess it'1 only 1 parameter
ri -Path a.txt,b.txt -Force
gr /\/\o\/\/
Keith Hill [MVP] wrote:
"Marcel J. Ortiz Soto [MSFT]" <mosoto@xxxxxxxxxxxxxxxxxxxx> wrote in message news:%23QJtC2waGHA.4060@xxxxxxxxxxxxxxxxxxxxxxx.I agree, its unfortunate we need this, but its the kind of tradeoff we have to make because PowerShell is both a shell and a scripting language. In shells people are used to using space as the delimiter.
copy a.txt b.txt
move a.txt b.txt
netstat -p tcp
Thus we need to support whitespace as a parameter delimiter. Other programming languages on the other hand, don't need to support this.
Careful there. I can't do this:
ri a.txt b.txt
I have to specify it like so:
ri a.txt, b.txt
This has bitten me a couple of times until I remember that I have to use a comma.
We know people get really attached to their coding styles and this might cause them some grief at first but hopefully they'll be able to live with this. Its not a change we made lightly. Try it out. If people still can't get used to this after some time then go ahead and open a feature request bug asking us to change it back.
I agree with dreeschkind, I never liked whitespace between a function name and parens. So I'm OK with this change - at least for now. :-)
--
Keith
- References:
- Re: [PSH] Methods/functions and blank spaces
- From: Marcel J. Ortiz Soto [MSFT]
- Re: [PSH] Methods/functions and blank spaces
- From: Marcel J. Ortiz Soto [MSFT]
- Re: [PSH] Methods/functions and blank spaces
- From: Keith Hill [MVP]
- Re: [PSH] Methods/functions and blank spaces
- Prev by Date: Re: PowerShell / get-childitem behavior....
- Next by Date: Re: [MSH] The new name is: Windows Power Shell
- Previous by thread: Re: [PSH] Methods/functions and blank spaces
- Next by thread: Re: [PSH] Methods/functions and blank spaces
- Index(es):
Relevant Pages
|