From: "Mark C. Chu-Carroll" <carroll@louie.udel.edu>
To: caml-list@pauillac.inria.fr
Subject: Dynamic linking in CSL?
Date: Fri, 22 Dec 1995 14:09:29 -0500 [thread overview]
Message-ID: <9512221909.aa01551@auriga.cis.udel.edu> (raw)
Is it possible, in CSL, to dynamically load and link a CSL module
which matches a static signature?
(I'm writing an editor, which provides mechanisms for user implemented
enhancements. Most enhancements work as external programs that communicate
with the editor through sockets. But I'd like users to be able to write
enhancements that use the TK binding to alter window behavior. The
only way for them to do such a thing without recompiling the editor
would be to have some sort of dynamic loading. I can handle type safety
by forcing extension packages to comform to a particular signature. But
I really need to have dynamic linking/loading.)
<MC>
next reply other threads:[~1995-12-28 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-22 19:09 Mark C. Chu-Carroll [this message]
1995-12-28 15:08 ` Francois Rouaix
1995-12-29 14:06 ` Mark C. Chu-Carroll
1995-12-30 10:45 ` Francois Rouaix
1995-12-28 16:13 ` Xavier Leroy
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=9512221909.aa01551@auriga.cis.udel.edu \
--to=carroll@louie.udel.edu \
--cc=caml-list@pauillac.inria.fr \
/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