caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alex Cowie <cowie@cs.unisa.edu.au>
To: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Camlp4 documentation
Date: Fri, 18 Feb 2005 19:24:14 +1030	[thread overview]
Message-ID: <4215AD36.1070303@cs.unisa.edu.au> (raw)
In-Reply-To: <4215A18C.7040603@barettadeit.com>

Alex Baretta wrote:

> Martin Jambon wrote:
>
>> On Thu, 17 Feb 2005, Christian Szegedy wrote:
>>
>>
>>> Feel free to write your CamlP4 extension ;)
>>
>>
>>
>> :-)
>> But there are few things to know/discover before starting.
>>
>> Is anyone interested in a kind of highly practical tutorial on
>> how to extend the syntax of OCaml with Camlp4?
>> I could possibly start writing one if there is enough demand.
>>
>>
>> Martin
>>
>
> Why yes! Yet, it's terribly sad that DdR chose to forcibly impose upon 
> the Camlp4 metaprogrammer to use the revised syntax. This is probably 
> the main obstacle, together with the relative lack of documentation, 
> to the diffusion of Camlp4, IMHO.
>
> Alex
>
For me, the use of revised syntax has been a disincentive to using 
Camlp4 metaprogramming.  I have always wondered whether a traditional 
syntax version of Camlp4 was technically feasible.  Any comments?

Alex Cowie

--
School of Computer and Information Science
University of South Australia


  reply	other threads:[~2005-02-18  8:54 UTC|newest]

Thread overview: 32+ 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 [this message]
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
2005-02-24 15:24                 ` William D. Neumann
2005-02-18  8:14     ` [Caml-list] Camlp4 documentation (was: Immediate recursive functions) Robert M. Solovay
2009-05-23 12:24 Camlp4 documentation Jon Harrop
2009-05-23 13:13 ` Re : [Caml-list] " Matthieu Wipliez
2009-05-23 17:37   ` Christophe TROESTLER
2009-05-23 19:22     ` Jon Harrop
2009-05-23 19:55       ` Christophe TROESTLER

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=4215AD36.1070303@cs.unisa.edu.au \
    --to=cowie@cs.unisa.edu.au \
    --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;
as well as URLs for NNTP newsgroup(s).