Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
cduce
cduce
Commits
62c914e5
Commit
62c914e5
authored
Oct 05, 2007
by
Pietro Abate
Browse files
[r2004-03-13 16:14:51 by beppe] typos
Original author: beppe Date: 2004-03-13 16:14:51+00:00
parent
c05cb164
Changes
1
Hide whitespace changes
Inline
Side-by-side
web/manual/interface.xml
View file @
62c914e5
...
...
@@ -7,7 +7,7 @@
<p>
When you have to write a large program you often need to manage some
persistent data. A really elegant and widespread techni
c
, to fulfill
persistent data. A really elegant and widespread techni
que
, to fulfill
this goal, is to use XML based documents. And a really safe and robust
way to treat XML files is to write a small program in CDuce. In this,
section, we present a way to call CDuce functions from OCaml to
...
...
@@ -49,7 +49,7 @@ let f ( Int -> ML_int )
]]>
</sample>
<p>
And now the OCaml code in file,
<code>
foo.mli
</code>
(we use the blue color to highlight O
c
aml code):
And now the OCaml code in file,
<code>
foo.mli
</code>
(we use the blue color to highlight O
C
aml code):
</p>
<sample>
<![CDATA[
...
...
@@ -73,7 +73,7 @@ Note that there are two rules to respect when creating your interface file:
<li>
Every value defined in your OCaml file (
<code>
.mli
</code>
) has to
be defined in your CDuce file. Whereas the opposite is not
necessary: you can have much more (toplevel) values in your CDuce file than in
necessary: you can have much more (top
-
level) values in your CDuce file than in
your OCaml interface, only the latter are exported but the module.
</li>
<li>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment