From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Camlp4 with traditional syntax (was: Camlp4 documentation)
Date: Thu, 24 Feb 2005 01:47:48 +0100 [thread overview]
Message-ID: <20050224004748.GB461@first.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0502221538050.2887-100000@localhost>
On Tue, Feb 22, 2005 at 04:01:05PM -0800, Martin Jambon wrote:
> On Tue, 22 Feb 2005, Oliver Bandel wrote:
>
> [...]
> > Because I don't know about what you all are talking here,
> > I hope that the intended Camlp4-Tutorial will explain
> > such things in more detail.
>
> I started writing a tutorial this weekend. There are many things to say,
> and there are also many things that I ignore...
>
> > Not another "we know nearly all, and explain some nifty
> > details, that you also can see, when looking into the sources
> > and study them some months/years" documentation, please... :->
> >
> > So, if the indended doc on Camlp4 would
> > explain in detail what it is good for, what it
> > provides and how to use it, I (and IMHO many others)
> > would gain a lot of such a documentation/tutorial.
>
> I will try to talk about just what I know, not give too many technical
> details but rather pointers to the relevant sources of documentation or
> tips on "What should do in that case?".
>
> The goal is just to avoid anyone being stuck more than 2 minutes while
> trying to extend the syntax of OCaml.
Sounds good. :)
Hint:
"Just as a picture is worth a thousands words,
so is a properly chosen program example."
(Stephen G. Kochan, Programming in Objective C, page 2)
>
> > Explaining the details to pwople who already knew
> > the most stuff, IMHO is not really needed. This can be
> > done in discussions on the list (or when people
> > know the tools, they really can look into the sources,
> > because they know something about what they are intended to do).
> >
> > Hoping for a good intruductional tutorial...
>
> OK, I will try my best.
:)
Ciao,
Oliver
next prev parent reply other threads:[~2005-02-24 9:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 15:32 Immediate recursive functions Alex Baretta
2005-02-17 18:20 ` [Caml-list] " Marcin 'Qrczak' Kowalczyk
2005-02-17 19:00 ` Jason Hickey
2005-02-17 20:33 ` Alex Baretta
2005-02-17 19:18 ` Christian Szegedy
2005-02-17 20:36 ` Alex Baretta
2005-02-17 22:39 ` Camlp4 documentation (was: Immediate recursive functions) Martin Jambon
2005-02-17 23:30 ` [Caml-list] " Richard Jones
2005-02-17 23:51 ` Michael Walter
2005-02-18 0:51 ` Micha
2005-02-18 3:37 ` briand
2005-02-18 5:21 ` Oliver Bandel
2005-02-18 6:51 ` Johann Spies
2005-02-18 8:04 ` [Caml-list] Camlp4 documentation Alex Baretta
2005-02-18 8:54 ` Alex Cowie
2005-02-18 16:20 ` Camlp4 with traditional syntax (was: Camlp4 documentation) Hendrik Tews
2005-02-18 16:28 ` [Caml-list] " Alex Baretta
2005-02-18 22:36 ` Hendrik Tews
2005-02-21 12:28 ` Alex Baretta
2005-02-21 12:55 ` Bardur Arantsson
2005-02-21 15:22 ` [Caml-list] Camlp4 with traditional syntax Olivier Andrieu
2005-02-21 16:57 ` Bardur Arantsson
2005-02-18 18:43 ` [Caml-list] Camlp4 with traditional syntax (was: Camlp4 documentation) Martin Jambon
2005-02-18 22:41 ` Hendrik Tews
2005-02-22 10:29 ` Oliver Bandel
2005-02-22 23:32 ` Richard Jones
2005-02-23 0:01 ` Martin Jambon
2005-02-24 0:47 ` Oliver Bandel [this message]
2005-02-24 15:24 ` William D. Neumann
2005-02-18 8:14 ` [Caml-list] Camlp4 documentation (was: Immediate recursive functions) Robert M. Solovay
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=20050224004748.GB461@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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