From: "Rémi Dewitte" <remi@gide.net>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] Ad-hoc component system with a plug-in architecture
Date: Mon, 7 Nov 2011 17:01:56 +0100 [thread overview]
Message-ID: <CA+Whxo=Xfm_X-F=643PiTchBfkPaA9Z1RO2tdV0_EepczXa21A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Hello,
From the arcticle 'OCaml, the ultimate refactoring tool' [1] written by
Yaron Minsky, he writes :
"So, I replaced this ad-hoc component system with a plug-in architecture
where every component registered itself in a uniform way, with a flexible,
type-safe way for the components to communicate."
I am curious to know how you would build such a component system ?
I have tried to use dynlink library but found it difficult to deal with
because of dependencies. I have ended up using cppo as a macroprocessor and
ship various versions of my binary.
Cheers,
Rémi
[1] http://ocaml.janestcapital.com/?q=node/101
[-- Attachment #2: Type: text/html, Size: 753 bytes --]
reply other threads:[~2011-11-07 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+Whxo=Xfm_X-F=643PiTchBfkPaA9Z1RO2tdV0_EepczXa21A@mail.gmail.com' \
--to=remi@gide.net \
--cc=caml-list@inria.fr \
--cc=remi.dewitte@gide.net \
/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).