From: Quinn Dunkan <quinn@barf.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dhog the corruptor!
Date: Tue, 13 Nov 2001 16:34:24 -0800 [thread overview]
Message-ID: <20011114003429.34D279C404@barf.ugcs.caltech.edu> (raw)
In-Reply-To: Your message of "Tue, 13 Nov 2001 18:50:20 EST." <20011113235023.C50A519A4A@mail.cse.psu.edu>
> 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.
Yeah, trying to maintain static signatures is a whole other kettle of wax. I
was thinking of dynamically typed languages, though.
> > 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).
That'll work well enough for me. Single entry point could be a struct of
generic object pointers or a function that installs names in a namespace.
Cool!
forsyth:
> type checking is often ignored in these interfaces.
> with static linking #include and mk are often adequate if
> not perfect, but dynamic linking increases the chances for
> error.
AFAICT, though, dynamically typed languages don't have to worry about it.
Skeptics would say "that's because the chances for error are already at
maximum and can't be increased" :)
next prev parent reply other threads:[~2001-11-14 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 23:50 David Gordon Hogan
2001-11-14 0:34 ` Quinn Dunkan [this message]
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=20011114003429.34D279C404@barf.ugcs.caltech.edu \
--to=quinn@barf.ugcs.caltech.edu \
--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).