Commit 7c20712b authored by Pietro Abate's avatar Pietro Abate
Browse files

[r2005-08-24 16:54:55 by afrisch] Empty log message

Original author: afrisch
Date: 2005-08-24 16:54:55+00:00
parent eb7e4263
......@@ -35,17 +35,14 @@ been reused.
The build procedure for OCamlDuce is exactly the same as for OCaml:
<tt>configure, make world, make install</tt>. The names of the tools
are unchanged: <tt>ocaml,ocamlc,ocamlopt</tt>. Currently, OCamlDuce
is based on CVS snapshots of OCaml (between 3.08.3 and the current
<tt>release308</tt> branch) and CDuce (between 0.3.91 and the head).
is based on OCaml 3.08.4 and on a CVS snapshots
of CDuce (between 0.3.92 and the head).
version 0.0.5</a></li>
library, version 0.0.4</a></li>-->
version 3.08.4</a></li>
......@@ -1104,6 +1101,26 @@ tail-recursive way. You can safely use it on very long sequences.
<box title="OCaml and OCamlDuce" link="ocaml">
Since the 3.08.4 release, OCamlDuce is binary compatible with the corresponding
OCaml release. This means that OCamlDuce can use OCaml-generated
<tt>.cmi</tt> files and that it produces an OCaml-compatible
<tt>.cmi</tt> file if the interface does not use any x-type
(this file is equal to what would have been obtained by using OCaml).
It is thus possible to use existing libraries which were compiled for
OCaml 3.08.4. It is also possible to use OCamlDuce to compile
some modules and use them in an OCaml project provided their interface
is pure OCaml.
<box title="Code samples" link="code">
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment