From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Module hierarchies, aliasing, and dependencies
Date: Sun, 10 Sep 2000 22:16:14 +0100 [thread overview]
Message-ID: <E13YESW-00031m-00.2000-09-10-22-16-16@mail1.svr.pol.co.uk> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Sat, 09 Sep 2000 17:20:16 -0000." <1000909172016.ZM3792@candle.brasslantern.com>
"Bart Schaefer" wrote:
> Wouldn't it be better to rely on a symbol that's defined *inside* the
> module to determine whether a module has been loaded? Similar to the way
> (provides 'name) works in emacs libraries?
Yes, this sounds better. That would have fixed [some of] Will's
difficulties. Also, I've been wondering for a while how to provide a test
version of a module under a different name. This would be a good solution.
> One way to approach this would be to add another function, like the boot
> and cleanup functions that already exist, which is called when searching
> the list of modules. We could define this function to return a string
> that is compared to the module being searched for; or we could pass the
> string being searched for into the function and let it return a truth
> value. If the function isn't defined by a given module, then compare the
> name strings as is done now.
Given the way modules work, a function-based system is presumably the right
one.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk
next prev parent reply other threads:[~2000-09-10 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-09 17:20 Bart Schaefer
2000-09-10 21:16 ` Peter Stephenson [this message]
2000-09-10 21:35 ` Zefram
2000-09-10 22:29 ` Bart Schaefer
2000-09-14 15:18 ` Andrej Borsenkow
2000-09-14 16:36 ` Bart Schaefer
2000-09-14 17:15 ` Andrej Borsenkow
2000-09-15 18:14 ` Andrej Borsenkow
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=E13YESW-00031m-00.2000-09-10-22-16-16@mail1.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).