From: Chris Hecker <checker@d6.com>
To: Pierre Weis <Pierre.Weis@inria.fr>, fran@reyes.somos.net
Cc: caml-list@inria.fr
Subject: Re: Seeking pratical tutorial or examples.
Date: Mon, 16 Oct 2000 10:57:40 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20001016105132.02d96bd0@shell16.ba.best.com> (raw)
In-Reply-To: <200010160749.JAA21632@pauillac.inria.fr>
>> Isn't there a code snippet/samples page?
I think the ocaml docs are good, but I must agree with the original poster about one thing: there is a lack of small example programs that are meant to be _compiled_. That is, most of the examples use interactive mode. A few examples in particular would be good:
1. a single file ocaml program, and exactly how it's compiled with ocamlc and ocamlopt
2. a two file example, and how it's compiled (the .mli thing confused me for a while)
3. an example that uses an external C function
Since I wrote exactly these things, perhaps I should contribute them? I just found a lot of subtle things that were different between the interactive sessions and trying to write real code.
Chris
PS. Should the reply-to header on list messages be set to the list so threads don't accidently go private if somebody doesn't reply-all?
next prev parent reply other threads:[~2000-10-17 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-14 15:59 OCaml sync tool for Rex organizer bcpierce
2000-10-16 0:52 ` Seeking pratical tutorial or examples Francisco Reyes
2000-10-16 5:42 ` Alan Schmitt
2000-10-16 11:20 ` Francisco Reyes
2000-10-16 7:49 ` Pierre Weis
2000-10-16 17:57 ` Chris Hecker [this message]
2000-10-17 17:40 ` Stefan Monnier
2000-10-18 5:52 ` Francisco Reyes
2000-10-18 7:20 ` Chris Hecker
2000-10-18 13:31 ` Stephan Houben
2000-10-16 21:46 Brent Fulgham
2000-10-17 10:10 ` Francisco Reyes
2000-10-17 17:51 ` Chris Hecker
2000-10-18 5:58 ` Francisco Reyes
2000-10-17 19:21 Brent Fulgham
[not found] <20001019101803A.garrigue@kurims.kyoto-u.ac.jp>
2000-10-19 19:02 ` Francisco Reyes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20001016105132.02d96bd0@shell16.ba.best.com \
--to=checker@d6.com \
--cc=Pierre.Weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=fran@reyes.somos.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox