From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: hierarchical module names
Date: Wed, 15 Dec 1999 20:31:47 +0000 [thread overview]
Message-ID: <E11yL4P-0002Vt-00.1999-12-15-20-30-45@cmailg4.svr.pol.co.uk> (raw)
In-Reply-To: "Zefram"'s message of "Wed, 15 Dec 1999 10:52:15 GMT." <E11yC2a-0004gD-00@crucigera.fysh.org>
Zefram wrote:
> 3. Have alias modules for the historically-established names. We'd have,
> for example, a `zle' module, which has a built-in dependency on
> `zsh/zle' but doesn't actually do anything itself. So loading `zle'
> would have the effect of loading `zsh/zle', and zmodload would then
> report both `zle' and `zsh/zle' as loaded.
>
> I favour solution 3. It seems to maintain the greatest degree of
> compatibility, while not requiring any changes to the mechanism.
Perhaps we don't even need the aliased modules (though I don't quite know
how you'd plan to implement this anyway). zmodload could have a builtin
aliasing feature that says that zle is really zsh/zle; the relevant aliases
are set up. (This is at a low enough level that `zmodload -e zle'
etc. work too, of course.) If you could do the same thing with zmodload,
it would be a neat way of tricking zmodload for testing etc. --- e.g. you
unalias foo from standardmods/foo and alias it to testingmods/foo, then
anything which uses module foo still works with the other module, no fpath
trickery. This is how Stroustrup envisaged namespaces in C++ working, so
we'd be in quite good company.
I'll hold off sticking the patch into the development versions until some
sort of backward compatibility has emerged.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
prev parent reply other threads:[~1999-12-15 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-14 17:07 zefram
1999-12-14 23:45 ` Peter Stephenson
1999-12-15 10:52 ` Zefram
1999-12-15 20:31 ` 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=E11yL4P-0002Vt-00.1999-12-15-20-30-45@cmailg4.svr.pol.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--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).