caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alessandro Baretta <alex@baretta.com>
To: "Kontra, Gergely" <kgergely@mlabdial.hit.bme.hu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Threats on future of Camlp4
Date: Fri, 11 Oct 2002 14:56:59 +0200	[thread overview]
Message-ID: <3DA6CA9B.7020106@baretta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0210111314410.21652-100000@mlabdial.hit.bme.hu>



Kontra, Gergely wrote:
>>I want to make my contribution to this flamewar short:
>>
>> * Camlp4 is useful.
> 
> 
>>Otherwise, please resolve personal issues over a beer in a bar or in a
>>fight outside, whichever you prefer. As long as all of you stay healthy
>>for further development, OCaml-users will be happy... ;-)
> 
> 
> I agree, camlp4 IS useful. (Exploring the alternative syntax)
> I just afraid of developing in ocaml, if there exists two version of the
> syntax. ...
> 
> ps: If this was discussed, please tell me where can I read it.
> 
> Gergo

This was discussed on the mailing list. You can find 
previous threads in the archives. The main idea is that 
there is no need for a "standard" syntax, so long as CamlP4 
can always convert any nonstandard source code in the 
standard "vanilla" syntax.

Alex

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-10-11 12:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06 18:55 Daniel de Rauglaudre
2002-10-06 19:23 ` Chris Hecker
2002-10-06 19:52   ` Daniel de Rauglaudre
2002-10-06 21:01   ` brogoff
2002-10-06 21:09     ` Daniel de Rauglaudre
2002-10-06 19:29 ` Oleg
2002-10-06 20:01   ` Daniel de Rauglaudre
2002-10-06 20:24     ` Alessandro Baretta
2002-10-06 20:24       ` Daniel de Rauglaudre
     [not found]         ` <200210062143.g96Lhix15834@orchestra.cs.caltech.edu>
2002-10-07  2:47           ` Daniel de Rauglaudre
2002-10-06 20:28     ` Dave Mason
2002-10-06 20:50       ` Daniel de Rauglaudre
2002-10-06 20:45     ` Oleg
2002-10-06 21:03       ` Daniel de Rauglaudre
2002-10-06 21:46         ` Florian Douetteau
2002-10-07  2:56           ` Daniel de Rauglaudre
2002-10-06 23:54     ` Markus Mottl
2002-10-07  9:06       ` Daniel de Rauglaudre
2002-10-11 11:34       ` Kontra, Gergely
2002-10-11 12:56         ` Alessandro Baretta [this message]
2002-10-11 13:15         ` [Caml-list] Future " Daniel de Rauglaudre
2002-10-12 21:45           ` Oleg
2002-10-13  9:02             ` Daniel de Rauglaudre
2002-10-11 16:36         ` [Caml-list] Syntax brogoff
2002-10-07  7:21 ` [Caml-list] Threats on future of Camlp4 Sven LUTHER
2002-10-07  8:52   ` Daniel de Rauglaudre
2002-10-07 11:25     ` Sven LUTHER
2002-10-07 11:30       ` Daniel de Rauglaudre
2002-10-07 11:55         ` Sven LUTHER
2002-10-08  7:57     ` Alessandro Baretta
     [not found]       ` <nhalm59cf0s.fsf@malabar.mitre.org>
2002-10-08 14:05         ` Alessandro Baretta

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=3DA6CA9B.7020106@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=kgergely@mlabdial.hit.bme.hu \
    /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).