Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] ocaml and large development projects
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ 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)

> 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. 


To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: