Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: f() { ...; } > file
- X-seq: zsh-workers 26038
- From: Stephane Chazelas <Stephane_Chazelas@xxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Subject: Re: f() { ...; } > file
- Date: Thu, 13 Nov 2008 14:55:27 +0000
- In-reply-to: <20081113144212.GB5114@xxxxxxxxxxxxxxx>
- Mail-followup-to: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20081105212036.GA4698@xxxxxxxxxxxxxxx> <20081113144212.GB5114@xxxxxxxxxxxxxxx>
On Thu, Nov 13, 2008 at 02:42:12PM +0000, Stephane Chazelas wrote:
[...]
> The patch below seems to fix it. It just removes the special
> case of f() { }. I don't why it was there in the first place.
> rev 1.1 of parse.c already had it.
[...]
I had a look at the old releases. It looks like in the beginning
only the:
f() { ... }
syntax was supported (I'm not talking of the function foo {...}
ksh syntax here).
Then, as part of the "short loops" feature (disabled with setopt
noshortloops), support for:
f() any command
was added (but disabled upon setopt noshortloops).
Then later the check for noshortloops was removed, possibly by
someone who realised that "emulate sh" would set noshortloops
and therefore break compatibility with sh which allows f() cmd
Cheers,
Stéphane
Messages sorted by:
Reverse Date,
Date,
Thread,
Author