From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: zsh-workers@math.gatech.edu (Zsh hacking and development)
Subject: ((...)) fix
Date: Sun, 24 Nov 1996 01:03:06 +0100 (MET) [thread overview]
Message-ID: <199611240003.BAA02995@hzoli.ppp.cs.elte.hu> (raw)
There are two problems with the rewritten ((...)): it dumps core on (())
and it substitutes its body twice.
Zoltan
*** exec.c 1996/11/17 01:57:26 3.1.0.2
--- exec.c 1996/11/23 23:34:17 3.1.0.3
***************
*** 2356,2370 ****
int
execarith(Cmd cmd)
{
! char *e = (char *) getdata(firstnode(cmd->args));
! int val;
! singsub(&e);
! if (errflag)
! return 1;
! val = matheval(e);
errflag = 0;
! return(!val);
}
/* perform time ... command */
--- 2356,2368 ----
int
execarith(Cmd cmd)
{
! char *e;
! long val = 0;
! while ((e = (char *) ugetnode(cmd->args)))
! val = matheval(e);
errflag = 0;
! return !val;
}
/* perform time ... command */
reply other threads:[~1996-11-24 1:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199611240003.BAA02995@hzoli.ppp.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).