From: Geoffrey Alan Washburn <geoffw@cis.upenn.edu>
To: caml-list@inria.fr
Cc: caml-list@inria.fr
Subject: Re: OCaml bytecode documentation?
Date: Mon, 22 May 2006 17:53:26 -0400 [thread overview]
Message-ID: <447232D6.2070902@cis.upenn.edu> (raw)
In-Reply-To: <871wul3k0q.fsf@linux-france.org>
David MENTRE wrote:
> Geoffrey Alan Washburn <geoffw@cis.upenn.edu> writes:
>
>> Where would I look for more information about the bytecode
>> language used by current versions of OCaml? Is it still based upon CAM?
>
> Would this help?
> http://cristal.inria.fr/~lebotlan/docaml_html/english/english004.html
Probably, though why isn't this part of the "official" documentation,
or at least linked from, caml.inria.fr?
next prev parent reply other threads:[~2006-05-22 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 17:30 Geoffrey Alan Washburn
2006-05-22 20:02 ` [Caml-list] " David MENTRE
2006-05-22 21:53 ` Geoffrey Alan Washburn [this message]
2006-05-23 5:49 ` [Caml-list] " Alan Schmitt
2006-05-23 7:02 ` [Caml-list] doc licence (was: OCaml bytecode documentation?) Florent Monnier
2006-05-23 7:38 ` [Caml-list] Re: OCaml bytecode documentation? Francois Pottier
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=447232D6.2070902@cis.upenn.edu \
--to=geoffw@cis.upenn.edu \
--cc=caml-list@inria.fr \
/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