From: Zefram <zefram@tao.co.uk>
To: b.stephens@isode.com (Bruce Stephens)
Cc: zsh-workers@math.gatech.edu
Subject: Re: Associative arrays, structured namespaces
Date: Wed, 10 Jun 1998 11:44:51 +0100 (BST) [thread overview]
Message-ID: <199806101044.LAA12918@taos.demon.co.uk> (raw)
In-Reply-To: <vbaf7lzha2.fsf@snake.isode.com> from "Bruce Stephens" at Jun 10, 98 11:24:05 am
Bruce Stephens wrote:
>This strikes me as an excellent idea. Presumably the implementation
>is similar to that of associative arrays, though?
No. The way it's done in Elate, the shell just treats the structured
variable name as an opaque string. It's only convention that interprets
the name as having structure. Associative arrays is a completely
separate issue.
>What's then needed is some way of tying these names to other names, so
>that PATH connects correctly to shell.path and so on.
That's relatively easy. We already have some support for linked
parameters.
> This would be a
>good opportunity to generalise things a bit, and allow arbitrary shell
>functions to be called when a variable gets set or read, and stuff
>like that.
I'd like to do that too.
-zefram
next prev parent reply other threads:[~1998-06-10 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-09 17:09 User-defined zle widgets and built-in widget failure Bart Schaefer
1998-06-09 18:01 ` Zefram
1998-06-09 19:12 ` Bart Schaefer
1998-06-09 20:02 ` Zefram
1998-06-10 6:26 ` Variable namespaces, goals for ZLE, etc Bart Schaefer
1998-06-10 10:55 ` Zefram
1998-06-10 17:37 ` Bart Schaefer
1998-06-10 18:01 ` Zefram
1998-06-10 18:36 ` Bart Schaefer
1998-06-10 10:24 ` Associative arrays, structured namespaces Bruce Stephens
1998-06-10 10:44 ` Zefram [this message]
1998-06-10 12:07 ` Bruce Stephens
1998-06-10 12:28 ` Bruce Stephens
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=199806101044.LAA12918@taos.demon.co.uk \
--to=zefram@tao.co.uk \
--cc=b.stephens@isode.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).