Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Builtin strftime and TZ assignments

X-seq: zsh-workers 34598
From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
To: zsh-workers@xxxxxxx
Subject: Re: Builtin strftime and TZ assignments
Date: Sat, 21 Feb 2015 22:27:12 +0000
In-reply-to: <150221124546.ZM8579@torch.brasslantern.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
References: <CADjGqHvaOkB-T_qGHDvt9=8TzSGiR8-FptXCX8VNFyfPkmJN-g@mail.gmail.com> <CABx2=D9e8KPMd9fxL5UY5BoVOdnNyMx-d2tR3v_4Gmd7V5m7DQ@mail.gmail.com> <150221102305.ZM26540@torch.brasslantern.com> <150221124546.ZM8579@torch.brasslantern.com>

On Sat, 21 Feb 2015 12:45:46 -0800
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> However, I'm hoping someone (PWS?) can explain why the extra pm->level
> bump is necessary to get the parameter to be removed from the environment
> upon endparamscope().

I don't know.  Is it necessary?  The code in params.c that deals with
locallevel suggests it shouldn't be.

>+	    pm->level = locallevel + 1; /* copied from Zle/zle_params.c*/

In zle_params.c the parameter scope isn't supplied, instead it's
supplied by the surrounding code, so this might be caution, historical,
whatever.

pws

Follow-Ups:
- Re: Builtin strftime and TZ assignments
  - From: Bart Schaefer

References:
- Builtin strftime and TZ assignments
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author