From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Possible zsh bug with unique tied vars in 4.0.4?
Date: Tue, 11 Jun 2002 10:52:42 +0100 [thread overview]
Message-ID: <15870.1023789162@csr.com> (raw)
In-Reply-To: "Steve Simmons"'s message of "Mon, 10 Jun 2002 13:52:56 EDT." <20020610175255.GA10947@ans.net>
Steve Simmons wrote:
> The following sequence of commands shows unexpected performance in
> zsh when using tied variables and unique processing. In brief, if
> you have tied variables FOO and foo and typeset one of them to unique
> (-U), you can use the other to assign non-unique values to the first.
> This is counter-intuitive at best :-), and I can see no use for this
> feature. The manual page leads one strongly to believe that a single
> variable is created which simply has two names and two presentations;
> the experiment below shows that clearly there are other differences
> as well.
I think `strongly' is an overstatement since the manual page says the
two parameters `may otherwise be manipulated as normal' and indicates
that only the scalar can be exported. However, it's certainly not
particularly useful that -U works that way. It's more useful with some
of the other flags where you might want different padding (-L, -R, -Z)
or you might want to hide the value (-H) for just one of the parameters,
or mark just one of them as readonly (-r), even though these are
probably less used features. The only really good reason for not
changing this is that it makes a mess of the internals to grope around
for the alternative parameter just in the case where they are tied and
just for certain flags. I expect the documentation could be made more
explicit, though.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
prev parent reply other threads:[~2002-06-11 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 17:52 Steve Simmons
2002-06-11 9:52 ` Peter Stephenson [this message]
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=15870.1023789162@csr.com \
--to=pws@csr.com \
--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).