* [Caml-list] Ad-hoc component system with a plug-in architecture
@ 2011-11-07 16:01 Rémi Dewitte
0 siblings, 0 replies; only message in thread
From: Rémi Dewitte @ 2011-11-07 16:01 UTC (permalink / raw)
To: caml-list
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-11-07 16:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-07 16:01 [Caml-list] Ad-hoc component system with a plug-in architecture Rémi Dewitte
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox