caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Paolo Donadeo" <p.donadeo@gmail.com>
To: "OCaml mailing list" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Parsing simple type expressions
Date: Wed, 7 Jan 2009 23:50:45 +0100	[thread overview]
Message-ID: <4b5157c30901071450m7ab87d93yeb446dfee086b5f4@mail.gmail.com> (raw)
In-Reply-To: <524796.35746.qm@web27006.mail.ukl.yahoo.com>

Thanks, Matthieu and Jake, this is exactly what I had in mind.

At the end, Camlp4 was the right solution to my simple problem, as I
suspected from the beginning. Camlp4 is an extremely powerful tool and
it's a pity it couldn't be used by everyone for lack of documentation.
What is really needed, in my opinion, is a description of *what* one
can do with Camlp4 without being an expert. For example a list of all
syntax extension available out of the box might spread the use of
Camlp4 among common programmers.

Searching in the source code I can see things named:
Camlp4ExceptionTracer, Camlp4FoldGenerator, Camlp4MetaGenerator, and
so on. The names sounds great but... what is it? The source code is
cryptic to every "regular" OCaml programmer like me. The same
considerations apply to all the (many!) libraries available and
related to Camlp4.

What is needed to spread the use of this tool are some... recipes,
like those available for ocamlbuild in its wiki pages.


-- 
Paolo
~
~
:wq


  reply	other threads:[~2009-01-07 22:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 14:03 Paolo Donadeo
2009-01-06 15:12 ` [Caml-list] " David Allsopp
2009-01-06 21:10   ` Martin Jambon
2009-01-06 22:49     ` Re : " Matthieu Wipliez
2009-01-07 22:50       ` Paolo Donadeo [this message]
2009-01-06 18:19 ` Jake Donham
2009-01-06 21:00   ` Paolo Donadeo

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=4b5157c30901071450m7ab87d93yeb446dfee086b5f4@mail.gmail.com \
    --to=p.donadeo@gmail.com \
    --cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).