Hello,

It is a great pleasure to participate in this list. I'm
returning to Caml after using having used it on my XT back in
high school. I remember trying to stretch 640k for all it was 
worth in those days. I'm glad to see all the work that has gone
into it. Keep up the excellent work!

There have been questions raised about threading in Caml under
BeOS, but however no one has responded with authority to these.
I have a few more pragmatic questions related to this. BeOS
treats threads and sockets in a fundamentally different
(better?) way than POSIX. I would like to use Caml purely as
code generator and interface the native BeOS libraries via C.
Can I be safe is assuming that the GC facilities and in general
Caml runtime are thread-safe. What would be required to ensure
thread safety, since building with -with-pthread is not an
option on BeOS? Could I, if desperate enough, initialize
separate Caml runtimes by calling caml_main in different threads
from a C main program to avoid synchronization issues? Ideally
I'd like to strip any extraneous code in Caml that is associated
with a UNIX view of the world. If OCaml is not a option, how
about Caml Light? The language itself is worth the tradeoff in
execution speed.

I hope you can help.

Once more, many thanks to the researchers at INRIA. With all
these discussions about libraries and the such, I hope you keep
the system code clean and simple as it is right now. Less is
more, although this email seems to be the antithesis of this.

Anjayan
--
Hire a talented student for a summer internship.
http://www.student.math.uwaterloo.ca/~apuvanan/

-------------------
To unsubscribe, mail caml-list-request@inria.fr.  Archives: http://caml.inria.fr