zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: Zsh hackers list <zsh-workers@sunsite.dk>
Subject: Re: named references
Date: Wed, 27 Jun 2001 20:18:15 +0100	[thread overview]
Message-ID: <3B3A3177.4BA21665@u.genie.co.uk> (raw)
In-Reply-To: <Tc0a88d015467712d39@mailsweeper01.cambridgesiliconradio.com>

Peter Stephenson wrote:

> I'd certainly like to see this included, along with other stuff from ksh93
> unless it's obviously stupid.  The question is when to do it:  we have been
> planning a neatening up of the parameter setting code, which hasn't got an
> interface so much as a backend which happens to include a few functions

>From my perspective, with respect to `when', doing namerefs now allows
me to become more familiar with zsh's C code. Were you thinking of
doing a parameter rewrite soon?

I'd be interested in more detail on the ideas you have for the
parameter code. What sort of thing might the interface provide?

My main thoughts from what I've seen is that it would be good if it was
more flexible so that you could have something like an array of
assocations of floats. Maybe allow arrays of things of mixed type? What
other types might we want other than something like ksh namespaces
(records/structs or whatever you like to call them).

> callable from outside.  That would probably be a necessary prerequisite for
> any attempt at another ksh feature, the ability to tie getting and setting
> of parameters to shell functions.

Do you mean something like ksh93 discipline functions. If we were to be
compatible with ksh93, I think that would also require ksh namespaces
(but I'm not sure). Would it be useful if I post a list of ksh93
features not in zsh?

Bart Schaefer wrote:
> On Jun 27,  5:03pm, Oliver Kiddle wrote:

> I think they'd be a very useful addition.  Particularly if you can do:
> 
>         typeset -A hash
>         hash[key]=value
>         nameref 'thing=hash[key]'
> 
> Which, of course, would be easily implemented given my scheme of storing
> a pointer to the referenced node in the nameref node. :-)

Yes, that would be nice but not necessarily impossible with the string
instead of the pointer. I planned to try to get that working after I had
the basic ksh level of features working.

> You haven't answered any of my questions from 15059, though ...

It took me a while to go through it and think about all the options so I
did the quick reply to Andrej first.

Oliver


  reply	other threads:[~2001-06-27 19:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24 11:34 Oliver Kiddle
2001-06-24 18:28 ` Bart Schaefer
2001-06-27 19:01   ` Oliver Kiddle
2001-06-28  8:07     ` Andrej Borsenkow
2001-06-28  8:30       ` Bart Schaefer
2001-06-28  9:39     ` Peter Stephenson
2001-06-30  7:56       ` Bart Schaefer
2001-07-02  9:31         ` Peter Stephenson
2001-06-30  7:37     ` Bart Schaefer
2001-07-09 19:43       ` Oliver Kiddle
2001-06-25  5:19 ` Andrej Borsenkow
2001-06-27 16:03   ` Oliver Kiddle
2001-06-27 16:50     ` Peter Stephenson
2001-06-27 19:18       ` Oliver Kiddle [this message]
2001-06-30  8:09         ` Bart Schaefer
2001-06-27 17:14     ` Bart Schaefer

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=3B3A3177.4BA21665@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --cc=zsh-workers@sunsite.dk \
    /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).