From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Fabrice LE FESSANT <fabrice@ocamlpro.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml cheat sheets
Date: Mon, 6 Jun 2011 19:36:30 +0200 [thread overview]
Message-ID: <BANLkTimO2VWn+N8fqReZKy35b65K50DPvw@mail.gmail.com> (raw)
In-Reply-To: <4DED026D.4050002@ocamlpro.com>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
Impressive formatting. I can't imagine the dreadful time you've spent
checking each description to make sure it doesn't overflow the column width.
Some small remark:
First, I find the organization of the "Standard Library" one a bit
surprising; maybe ordering modules alphabetically would be better.
More importantly, I'm a bit disappointed by the "OCaml Standard Tools" one.
They don't mention ocamlbuild and ocamlfind which I use much more often and
would, I think, be more appropriate on a cheat sheet that relatively arcane
options of the compiler (which I don't think I could use from this cheat
sheet anyway, each time I touch -custom I need to re-read the documentation
in full). Of course ocamlfind is not part of the base distribution, but I
still think it is a "standard" tool.
Stretching it a bit, I don't use ocamlyacc anymore, as I found menhir [1] to
be a better replacement for all purposes. That's the one I would have chosen
for a cheatsheet -- but I understand the value of describing a tool included
in every OCaml installation.
[1] http://gallium.inria.fr/~fpottier/menhir/
Thanks for the work.
On Mon, Jun 6, 2011 at 6:38 PM, Fabrice LE FESSANT <fabrice@ocamlpro.com>wrote:
> Hi,
>
> We have published some "cheat sheets" on OCaml on OCamlPro's website:
>
> http://www.ocamlpro.com/code/2011-06-03-cheatsheets.html
>
> These cheat sheets are supposed to help developers to learn and to use
> OCaml by providing a condensed view of its documentation. Feel free to
> use them, distribute them to your students, and to tell us how we could
> improve them, what you think is important and should be added, etc.
>
> --
> Fabrice
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
[-- Attachment #2: Type: text/html, Size: 2704 bytes --]
next prev parent reply other threads:[~2011-06-06 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 16:38 Fabrice LE FESSANT
2011-06-06 17:15 ` Yoann Padioleau
2011-06-06 17:25 ` Török Edwin
2011-06-06 17:31 ` rixed
2011-06-06 17:36 ` Gabriel Scherer [this message]
2011-06-06 17:56 ` [Caml-list] " Sylvain Le Gall
2011-06-06 17:46 ` [Caml-list] " Gregory Bellier
2011-06-06 18:01 ` Stefano Zacchiroli
2011-06-07 15:49 ` Fabrice Le Fessant
2011-06-07 16:24 ` Stefano Zacchiroli
2011-06-07 17:00 ` Philippe Wang
2011-06-06 18:10 ` Andrew
2011-06-06 18:16 ` Gabriel Scherer
2011-06-06 22:28 ` Hai NGUYEN VAN
2011-06-06 22:03 ` Benjamin Canou
2011-06-07 5:55 ` [Caml-list] " Mihamina Rakotomandimby
2011-06-07 20:13 ` [Caml-list] " Paolo Donadeo
2011-06-08 6:46 ` Pierre Bourdon
2011-06-14 16:01 ` Ashish Agarwal
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=BANLkTimO2VWn+N8fqReZKy35b65K50DPvw@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=fabrice@ocamlpro.com \
/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