Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Kenneth Knowles <kknowles@soe.ucsc.edu>
To: Thomas Fischbacher <Thomas.Fischbacher@Physik.Uni-Muenchen.DE>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] How to raise_with_arg() a tuple?
Date: Fri, 8 Jul 2005 09:24:28 -0700	[thread overview]
Message-ID: <20050708162428.GA24033@tallman.kefka.frap.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0507081727090.25669@katrin.cip.physik.uni-muenchen.de>

On Fri, Jul 08, 2005 at 05:55:38PM +0200, Thomas Fischbacher wrote:
> Just as a further question, not to be meant as a suggestion or wishlist 
> item: would it be conceivable that, at some point in the future, all the 
> ocaml tools that operate on .ml files could accept different 
> official "syntax variants" (say, the present one and a cleaned up syntax 
> to be defined in the future), and dispatch between parsers via some 
> command line argument or argv[0]? So that minor issues with the syntax 
> could be repaired, should they turn out to be a problem.

This exists, and is called camlp4.  I'm not sure which, if any, of the tools
that operate on .ml files doesn't "support" it via easy command line flags.

There is even a revised syntax shipped with camlp4 which has curried variant
constructors like Haskell.  Unfortunately, there's a lot of stuff in there I
disagree with, like extra bracketing of many constructs.

Here it is:

http://pauillac.inria.fr/caml/camlp4/manual/manual007.html

Forgive me if you already know of this and I misinterpreted your question.
 
- Kenn


  reply	other threads:[~2005-07-08 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 18:05 Thomas Fischbacher
2005-07-07 18:42 ` [Caml-list] " Olivier Andrieu
2005-07-08 15:55   ` Thomas Fischbacher
2005-07-08 16:24     ` Kenneth Knowles [this message]
2005-07-08 16:58       ` Thomas Fischbacher

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=20050708162428.GA24033@tallman.kefka.frap.net \
    --to=kknowles@soe.ucsc.edu \
    --cc=Thomas.Fischbacher@Physik.Uni-Muenchen.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