From: Bruce Stephens <B.Stephens@isode.com>
To: ZSH workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: Reading completion manual
Date: 02 Mar 1999 17:29:25 +0000 [thread overview]
Message-ID: <vbr9r7u7ey.fsf@snake.isode.com> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of "Tue, 2 Mar 1999 20:20:12 +0300"
"Andrej Borsenkow" <borsenkow.msk@sni.de> writes:
> > I thought namespaces had been discussed before? What's the objection
> > to allowing "." in variable names, and regarding it as a component
> > delimiter in function/command names?
>
> I spoke about functions not variables. Variables names are limited to
> alphanumeric, so you can safely use ``.'' as delimiter. Function names can
> be arbitrary (am I wrong?)
I don't see that it matters (practically). "_" is a non-optimal
choice, since people already use it too much, but some other prefix
would be OK, and it could be "zle." or "compctl." or something (i.e.,
looking like namespaces).
> Hmm, this isn't a good idea; I
> > quite often use things like "cp $i $i.bak" and stuff.
>
> If I remember correctly, it should start with a dot. And of course, you can
> use braces as usual
>
> cp ${.myvars.i} ${.myvars.i}.bak
>
> But you are right, it can break some scripts
Ah, OK. That's less confusing than my notion of predeclaring
namespaces. In that case, functions could do the same---
".zle.path_files"---or whatever. That's not likely to conflict with
ordinary usage.
> > (So if you have a function foo.WRITE, then that gets called when you
> > try to write to foo. Something like that, anyway. A better interface
> > might be to copy the Perl tie ideas---allowing special associative
> > arrays and things as Bart suggested; you wouldn't need name spaces for
> > this, of course.)
> >
>
> May be, simply add ZSH emulation module to Perl :-))) But yes, what
> you've just described is my long cherished idea.
Yes, it's a natural extension to zsh-with-associative-arrays. But
it's orthogonal to variable namespaces.
next prev parent reply other threads:[~1999-03-02 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-02 16:52 Andrej Borsenkow
1999-03-02 17:09 ` Bruce Stephens
1999-03-02 17:20 ` Andrej Borsenkow
1999-03-02 17:29 ` Bruce Stephens [this message]
1999-03-03 9:29 Sven Wischnowsky
1999-03-04 5:50 ` Bart Schaefer
1999-03-03 13:34 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=vbr9r7u7ey.fsf@snake.isode.com \
--to=b.stephens@isode.com \
--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).