Browse thread
[Caml-list] ocaml and large development projects
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Wolfgang Müller <Wolfgang.Mueller2@u...> |
| Subject: | [Caml-list] ocaml as *.so (was: ...and large development projects) |
Hi, > PS. A related issue is going to come up with respect to disabling > cross-file inlining when we get native DLLs. You want to be able to > control what gets made available for inlining when building a DLL, since > one of the uses of DLLs is to be able to supply a new version of code and > so you can't have it be already inlined in the client application. I would like to rephrase the question: is it possible to use OCaml code (plus possibly some C code) for generating dynamically linked libraries that are used as easily as c(++) from c(++)? I've got the impression that this is the case. At least page 218 of the docs (chapter 17.7. at the end) suggests so. As I am currently deciding if I want to start a project in OCaml that possibly could become a library that would have to be used from C or JAVA, I would be very interested in the OCaml-Gurus' comment on that. Cheers, Wolfgang ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners