Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: anonymous functions, full patch
- X-seq: zsh-workers 25257
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: PATCH: anonymous functions, full patch
- Date: Mon, 30 Jun 2008 16:04:32 +0100
- In-reply-to: <080630065737.ZM3284@xxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <18441.1214488302@xxxxxxx> <9646.1214491732@thecus> <200806261506.m5QF6aCd019139@xxxxxxxxxxxxxx> <080626101233.ZM2893@xxxxxxxxxxxxxxxxxxxxxx> <200806261729.m5QHSr5F021201@xxxxxxxxxxxxxx> <20080630112722.3e7eb215@news01> <080630065737.ZM3284@xxxxxxxxxxxxxxxxxxxxxx>
Bart Schaefer wrote:
> Seems a little odd, though, to call something a function when you can't
> pass any arguments to it. I'm not going to have time to look today, but
> how difficult is this?
>
> function { print $@ } args go here
Shouldn't be too horrific, but will require parsing changes, which is
why I didn't puruse it.
> Two final remarks: One: should this be considered a bug?
>
> torch% torch% () ()
> function function> {
> function function> print oops
> function function> }
> zsh: parse error near `\n'
>
> Once you've got the double empty parens there seems to be nowhere to go
> that doesn't end in a parse error.
Doesn't really surprise me.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author