zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-users mailing list <zsh-users@sunsite.dk>
Subject: Re: Real KSH93 is finally free software!
Date: Tue, 12 Apr 2005 18:20:23 +0200	[thread overview]
Message-ID: <26858.1113322823@trentino.groupinfra.com> (raw)
In-Reply-To: <1050412151712.ZM28145@candle.brasslantern.com>

Bart wrote:
> 
> Actually they *are* particularly tricky, because of the way zsh's nested
> parameter expansion passes data around.  Our first attempt to implement
> namerefs was what led to ${(P)var}.

For namerefs, the main job is cleaning up typeset code to not keep
disposing of parameters and recreating them anew. The typeset code is
also cluttered with special cases for handling special variables. So
some form of primitive typeset function needs to go in the _gsu struct.

> Discipline functions are ugly because in order to set them the parser has
> to implement the other missing bit of ksh syntax, which is namespaces as
> in ${foo.bar}.  Zsh doesn't allow "." as a valid character in variable

The ksh93 implementation of discipline functions doesn't cope well with
the fact that functions don't follow parameter scoping rules. So any
implementation of discipline functions may be better off using a
different design, incompatible with ksh.

Compound variables, namespaces and static scoping are higher on my
wishlist anyway.

Oliver


  reply	other threads:[~2005-04-12 16:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  5:12 Juhapekka Tolvanen
2005-04-12  5:34 ` Bart Schaefer
2005-04-12 12:11   ` Juhapekka Tolvanen
     [not found]     ` <juhtolv@cc.jyu.fi>
2005-04-12 12:38       ` Peter Stephenson
2005-04-12 13:22         ` Nikolai Weibull
2005-04-12 15:17         ` Bart Schaefer
2005-04-12 16:20           ` Oliver Kiddle [this message]
2005-04-12 17:01             ` 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=26858.1113322823@trentino.groupinfra.com \
    --to=okiddle@yahoo.co.uk \
    --cc=zsh-users@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).