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

Re: [PATCH 0/2] persistent locals (sort of)

X-seq: zsh-workers 52119
From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
To: Zsh hackers list <zsh-workers@xxxxxxx>
Subject: Re: [PATCH 0/2] persistent locals (sort of)
Date: Wed, 6 Sep 2023 16:38:40 -0700
Archived-at: <https://zsh.org/workers/52119>
In-reply-to: <CAH+w=7Ycj3i3oktyVPbSC_sYacOZz8kO48mPSno8ECJeKY61EA@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <CAH+w=7Ycj3i3oktyVPbSC_sYacOZz8kO48mPSno8ECJeKY61EA@mail.gmail.com>

Attempted to send these far enough apart that the article number
sequence would match the subject number sequence, but oh well.

On Tue, Sep 5, 2023 at 10:04 PM Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
>
> The argument list is then walked and [...]  Every name is prefixed
> with the namespace and checked for existence; iff it doesn't yet exist
> in the namespace, it's created with the specified value if any.
> Finally, and always, all the original names are created as named
> references to their counterpart in the namespace, using the hideval
> option from Part 1.

I just noticed that the comment in Part 2 has this in the other order.
My thought was that if there were any problem creating the named
references, the namespace should not get populated, but when it came
to making it all work the other order was more natural.  Can anyone
think of a way it's likely to go wrong?  (Is anyone [else] interested
enough for me to bother?)

References:
- [PATCH 0/2] persistent locals (sort of)
  - From: Bart Schaefer

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