From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: Namespaces again (was: RE: PATCH: Add jobdirs association to parameter module)
Date: Tue, 14 Dec 1999 17:18:01 +0300 [thread overview]
Message-ID: <000401bf463e$0779c240$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199912141333.OAA03823@beta.informatik.hu-berlin.de>
> Well, if someone wants to see if he can find any problems with this,
> it would be the patch below...
Is this really all that is needed? If I understand it correctly, this patch
simply makes `.' valid character for parameter names. It means, that both foo
and .bar.foo are put in the same (and the only) table ... both are happily
listed with `set' ... what's worse, it makes `foo.bar' hihgly ambiguous. It may
break scripts that do not expect `.' in parameter names ...
I'd expect `.' be treated as names separator - and only in context `.foo.bar'.
Thus `foo.bar' as identifier remains invalid alltogether (eliminating $foo.bar
ambiguity). We'll have default namespace for all names without dot and explicit
namespaces for name starting with dot. All commands should behave just as normal
Unix :-) - everything starting with dot is "hidden" by default. This should have
the minimum impact (as long, as users do not request namespaces, they simply do
not see them at all).
/andrej
next prev parent reply other threads:[~1999-12-14 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 13:33 PATCH: Add jobdirs association to parameter module Sven Wischnowsky
1999-12-14 14:18 ` Andrej Borsenkow [this message]
1999-12-14 14:30 Namespaces again (was: RE: PATCH: Add jobdirs association to parameter module) Sven Wischnowsky
1999-12-14 23:46 ` Peter Stephenson
1999-12-15 10:28 ` Zefram
1999-12-15 8:24 Sven Wischnowsky
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='000401bf463e$0779c240$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).