From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhog the corruptor!
Date: Tue, 13 Nov 2001 18:50:20 -0500 [thread overview]
Message-ID: <20011113235023.C50A519A4A@mail.cse.psu.edu> (raw)
> This is just for kernel drivers, right?
No, it's a general purpose mechanism. It's currently only used
for kernel device drivers, but I have my eyes on certain user
mode applications that could benefit.
> While plan9's non-support of dynamic
> linking for arbitrary C programs works just fine, it doesn't seem to work so
> well for languages that only load libraries at run time, such as python or
> perl (or limbo?).
I don't care about python or perl (so shoot me!). But my experiences
with limbo have taught me that loadable modules can be a powerful
tool. Limbo also has type signatures, which I have no plans to add
at this stage.
> If the linker can write relocation information, would that
> make it easier to write a dlopen()-like function?
We're not trying to load actual libraries here, but rather modules
of executable code. Said modules will have a single entry point
(which can be a struct, as it is for device drivers).
next reply other threads:[~2001-11-13 23:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 23:50 David Gordon Hogan [this message]
2001-11-14 0:34 ` Quinn Dunkan
2001-11-14 4:46 ` Lucio De Re
2001-11-16 11:52 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 9:26 forsyth
2001-11-16 11:56 ` Boyd Roberts
2001-11-13 23:54 forsyth
2001-11-13 23:53 David Gordon Hogan
2001-11-13 23:04 David Gordon Hogan
2001-11-13 23:28 ` Quinn Dunkan
2001-11-13 23:38 ` Chris Hollis-Locke
2001-11-13 22:53 anothy
2001-11-13 22:59 ` George Michaelson
2001-11-13 22:32 David Gordon Hogan
2001-11-13 22:09 anothy
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=20011113235023.C50A519A4A@mail.cse.psu.edu \
--to=dhog@plan9.bell-labs.com \
--cc=9fans@cse.psu.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.
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).