From: Wolfram Kahl <kahl@cas.mcmaster.ca>
To: caml-list@inria.fr
Subject: Re: [Caml-list] The solution to the syntax war
Date: Tue, 5 Feb 2002 14:32:06 -0500 [thread overview]
Message-ID: <200202051932.g15JW6104877@solon.cas.mcmaster.ca> (raw)
In-Reply-To: <20020205193258.C32589@gogol.zorgol> (message from Berke Durak on Tue, 5 Feb 2002 19:32:58 +0100)
Berke Durak <berke@altern.org> wrote:
> I think the Caml team should impose a new syntax with the next big change
> in Ocaml.
And if they really do it, they should make the syntax
look more like Haskell ;-)
How about a new OCaml-syntax-list?
Wolfram, who has changed from Caml Special Light to Labl Special Light,
then through all versions of OLabl, and back to OCaml through all its
labelised variants starting from 2.99 (with 30kloc) ...
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2002-02-05 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 18:32 Berke Durak
2002-02-05 19:32 ` Wolfram Kahl [this message]
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=200202051932.g15JW6104877@solon.cas.mcmaster.ca \
--to=kahl@cas.mcmaster.ca \
--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