From: Christian Gillot <cgillot@gruposbd.com>
To: caml-list@inria.fr
Subject: [Caml-list] Syntax change
Date: Tue, 05 Feb 2002 11:50:59 +0100 (CET) [thread overview]
Message-ID: <1012906259.3c5fb91341efb@webmail.sbdconsultors.com> (raw)
Hi,
As a newbie, I feeled puzzled by the fact that there's two
syntaxes for ocaml. I understand camlp4 is really useful to
extend ocaml on a _project-basis_ but it's awkward that there
is two syntaxes for ocaml. It's pretty clear that the revised
syntax is a progress. Nevertheless, it'll stay in its current
confidential use as long as it's not the default syntax, aka the
standard syntax. Because the newbie will have a natural tendance
to use the "standard" syntax.
Moreover as I said before it's puzzling to have two syntaxes widely
used. Which one use ? And if you use one, when you'll see the other
one you'll say : What do this code mean ? That's why all the ocaml
keywords are only avaible and used in english rather than alse
a french version, a deutsch version, etc. Clearly we need a compromise.
As Daniel said before the INRIA team will not push forward another
syntax. So what about the process in which is involved Perl6 ? I mean
all the talented people write RFC and let the users comment them in order
to reach a benefit for everybody ? That would be great and moreover
a "open" approach to the problem.
My 0.02
--
Christian Gillot <cgillot@gruposbd.com>
GNU/Linux developer
-------------------
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
next reply other threads:[~2002-02-05 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 10:50 Christian Gillot [this message]
2002-02-05 16:52 ` [Caml-list] Duplicated messages Mattias Waldau
2002-02-05 18:07 ` Matti Jokinen
2002-02-06 7:16 ` malc
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=1012906259.3c5fb91341efb@webmail.sbdconsultors.com \
--to=cgillot@gruposbd.com \
--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