Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
PATCH: 3.1.6: Parsing optimization bug
- X-seq: zsh-workers 8385
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: PATCH: 3.1.6: Parsing optimization bug
- Date: Sun, 24 Oct 1999 04:43:40 +0000
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
I'd appreciate it if someone could tell me why parsing whatever follows
"foo()" is different depending on whether "function" appeared before it.
Nevertheless, it's certainly not right to throw away the parse entirely.
zagzig[54] foo() echo bar
zagzig[55] foo
zagzig[56] functions foo
foo () { }
zagzig[57]
Index: Src/parse.c
===================================================================
@@ -1078,6 +1078,7 @@
sl->left = pl = (Pline) allocnode(N_PLINE);
pl->type = END;
pl->left = par_cmd();
+ c->u.list = l;
}
cmdpop();
c->type = FUNCDEF;
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author