From: Xavier Leroy <xavier.leroy@inria.fr>
To: Jenda Krynicky <Jenda@Krynicky.cz>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] DLLs or COM (was: ISAPI filter)
Date: Fri, 12 Oct 2001 16:27:32 +0200 [thread overview]
Message-ID: <20011012162732.E18676@pauillac.inria.fr> (raw)
In-Reply-To: <3BC6DCE3.28395.36C265A@localhost>; from Jenda@Krynicky.cz on Fri, Oct 12, 2001 at 12:06:59PM +0200
> Can you produce an ordinary Windows DLL with OCaml?
> Can you use a function to that you got a pointer and whose C style
> header you know?
> Can you access C style structures you got a pointer to from
> somewhere?
Yes, all this can be done with the help of some C stub code. You need
to compile the Caml code to a C object file (option -output-obj),
then write a bit of C stub code to give a C interface to your Caml
code. Finally, the C object file generated by Caml can be linked with
the stub code and the Caml runtime system to produce a DLL. Not
completely trivial, but doable.
> A related question :
> Can you use COM objects with OCaml?
> Can you create COM objects with OCaml?
The CamlIDL tool (http://caml.inria.fr/camlidl/) lets you create and
use COM components in Caml. It automates the creation of the C stub
code mentioned earlier, and also comes with handy scripts to help
building the DLL as described above.
> Can those objects be poolable?
I don't know what a "poolable object" is.
- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-10-12 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 17:08 [Caml-list] ISAPI filter Jenda Krynicky
2001-10-12 10:06 ` [Caml-list] DLLs or COM (was: ISAPI filter) Jenda Krynicky
2001-10-12 14:27 ` Xavier Leroy [this message]
2001-10-12 15:06 ` Jenda Krynicky
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=20011012162732.E18676@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=Jenda@Krynicky.cz \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).