From: Zefram <zefram@dcs.warwick.ac.uk>
To: hzoli@ny.frontiercomm.net (Zoltan Hidvegi)
Cc: wjf103@york.ac.uk, zsh-workers@math.gatech.edu
Subject: Re: modules!??
Date: Thu, 5 Jun 1997 18:33:10 +0100 (BST) [thread overview]
Message-ID: <10020.199706051733@jelly.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199706050545.BAA06291@hzoli.home> from "Zoltan Hidvegi" at Jun 5, 97 01:45:23 am
Zoltan Hidvegi wrote:
> Perhaps the output of zmodload should include the
>statically linked modules as well (with some indication that this module is
>static).
Probably a good idea. It should refuse to load the redundant dynamic
module, and refuse to unload the static module.
>Deltochar have a similar problem, it wants to use the zmod symbol exported
>by the zle module. The symbols defined by a module can be discovered using
>dlsym even on these systems, so we may find some way to overcome this
>limitation. I think it is possible to do that with some script-generated C
How? Would this be a case of #defining all imported symbols to
(*symbol_table[SYMBOL_NUM]) and having the module base manage home-made
symbol tables? If so, what do we do about systems where there are
several sizes of pointer?
> The imported function list is hard to portably generate
>automatically,
What's wrong with `nm obj.o | grep " U "` and comparing against the
lists of exported symbols? This could even be used to generate module
dependencies automatically.
-zefram
next prev parent reply other threads:[~1997-06-05 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-05 1:35 modules!?? Wez Furlong
1997-06-05 5:45 ` modules!?? Zoltan Hidvegi
1997-06-05 17:33 ` Zefram [this message]
1997-06-05 18:24 ` modules!?? Zoltan T. Hidvegi
1997-06-05 19:11 ` modules!?? Zefram
1997-06-05 19:22 ` modules!?? Zoltan T. Hidvegi
1997-06-05 19:46 ` modules!?? Zoltan T. Hidvegi
1997-06-07 19:48 ` modules!?? Stefan Monnier
1997-06-08 11:49 ` modules!?? Zefram
1997-06-05 12:33 modules!?? Wez Furlong
1997-06-05 14:17 ` modules!?? Peter Stephenson
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=10020.199706051733@jelly.dcs.warwick.ac.uk \
--to=zefram@dcs.warwick.ac.uk \
--cc=hzoli@ny.frontiercomm.net \
--cc=wjf103@york.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).