From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Modules dependencies RE: PATCH: zftp/tcp abstraction
Date: Wed, 27 Jun 2001 15:19:42 +0100 [thread overview]
Message-ID: <Tc0a88d015466e717c3@mailsweeper01.cambridgesiliconradio.com> (raw)
In-Reply-To: ""Andrej Borsenkow""'s message of "Wed, 27 Jun 2001 18:10:41 +0400." <004401c0ff12$f2d62ab0$21c9ca95@mow.siemens.ru>
"Andrej Borsenkow" wrote:
> > The other advantage of this is that, as Sven has pointed out, we
> > can handle
> > systems with RTLD_LAZY by loading first and asking questions afterwards.
> > The difference between these two methods is then transparent to the user
> > --- we don't have extra files on some systems and not on others.
> >
>
> Zeram/14786
>
> This was my original suggestion. Zefram had arguments against it.
I'm not sure Zefram's objection applies when RTLD_LAZY is around? He was
saying you can't load the module until you've fixed the depencies. In this
particular case, you can.
> I never liked inter-module data references. Is there any chance we can get
> rid of them and replace by wrappers/hooks/callbacks/what-ever? At least, as
> long-term goal?
I'd be entirely in favour of this. I'm not sure how easy it is, though.
I believe (without checking) that Sven has added plenty of scope for
hooks.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, 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.
**********************************************************************
next prev parent reply other threads:[~2001-06-27 14:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 16:26 Clint Adams
2001-06-06 16:34 ` Module namespaces? " Andrej Borsenkow
2001-06-06 16:37 ` Zefram
2001-06-06 18:07 ` Peter Stephenson
2001-06-06 19:12 ` Clint Adams
2001-06-07 8:13 ` Andrej Borsenkow
2001-06-07 9:41 ` Modules dependencies " Andrej Borsenkow
2001-06-07 10:00 ` Peter Stephenson
2001-06-07 10:18 ` Zefram
2001-06-07 13:16 ` Sven Wischnowsky
2001-06-07 13:35 ` Andrej Borsenkow
2001-06-07 15:31 ` Bart Schaefer
2001-06-14 9:33 ` Andrej Borsenkow
2001-06-26 11:26 ` Andrej Borsenkow
2001-06-26 16:33 ` Bart Schaefer
2001-06-30 11:24 ` Zefram
2001-06-27 13:49 ` Clint Adams
2001-06-27 13:59 ` Peter Stephenson
2001-06-27 14:10 ` Andrej Borsenkow
2001-06-27 14:19 ` Peter Stephenson [this message]
2001-06-27 18:42 ` Bart Schaefer
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=Tc0a88d015466e717c3@mailsweeper01.cambridgesiliconradio.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).