By "component", I mean an object with methods, asynchronous events, and
settable properties, working in containers that know how to embed these
components.  The origin of this approach was (I think) the Andrew project at
CMU, many years ago.  ML modules are different.

As for whether these are "right" or "wrong", this depends on whether you
want to work in a small purist community or interact with the wider world.
To date, OCaml has emphasised interoperability (e.g. with C), which is one
of the reasons that its been successful.

Dave.

-----Original Message-----
From: John Max Skaller [mailto:skaller@ozemail.com.au]
Sent: Thursday, January 11, 2001 6:38
To: Dave Berry
Cc: Markus Mottl; OCAML
Subject: Re: JIT-compilation for OCaml?


> 4.  A growing number of commercial offerrings are based on component
> technology (ActiveX controls or Javabeans).  Support for these (or perhaps
a
> native equivalent) would be very useful.  (Again, this is easier said than
> done).

	I guess these things have the wrong kinds of 'component'.
Ocaml already has the 'right' kind of component: the module.
What is needed is to dynamically load them (i.e. some module
conforming to some statically specified interface).