zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: PATCH: 3.1.4: Re: zsh bug with local variables?
Date: Tue, 18 Aug 1998 09:01:47 -0700	[thread overview]
Message-ID: <980818090148.ZM5899@candle.brasslantern.com> (raw)
In-Reply-To: <199808181451.QAA03048@hydra.ifh.de>

On Aug 18,  4:51pm, Peter Stephenson wrote:
} Subject: PATCH: 3.1.4: Re: zsh bug with local variables?
}
} !     /* If this was a local variable, we need to keep the old     *
} !      * struct so that it is resurrected at the right level.      *
} !      * This is partly because when an array/scalar value is set	 *
} !      * and the parameter used to be the other sort, unsetparam() *
} !      * is called.  Beyond that, there is an ambiguity:  should	 *
} !      * foo() { local bar; unset bar; } make the global  bar	 *
} !      * available or not?  The following makes the answer "no".   */

That's consistent with the 3.0.5 behavior.  Remember my namedir tests?
With this patch applied, 3.1.4 behaves exactly like 3.0.5 again:

zagzig% namedir_test
zsh 3.1.4
TEST 1
namedir1: test1=/etc
namedir1: test1=/etc
namedir2: test1=/etc
namedir1: test1=/etc
namedir3:
namedir1: test1=/etc
namedir4:
TEST 2
namedir1: test2=/etc
namedir1: test2=/etc
namedir2: test2=/etc
namedir1: test2=/etc
namedir3:
namedir1: test2=/etc
namedir4: test2=/usr/bin

(I still think the namedir4 behavior is wrong.)

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1998-08-18 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-18 13:37 Greg Klanderman
1998-08-18 14:51 ` PATCH: 3.1.4: " Peter Stephenson
1998-08-18 16:01   ` Bart Schaefer [this message]

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=980818090148.ZM5899@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).