From: "Kontra, Gergely" <kgergely@mlabdial.hit.bme.hu>
To: Stefano Zacchiroli <zack@cs.unibo.it>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CamlP4 Revised syntax comment
Date: Mon, 28 Oct 2002 09:38:04 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.21.0210280927120.26219-100000@mlabdial.hit.bme.hu> (raw)
In-Reply-To: <20021026092737.GC15534@cs.unibo.it>
>It's an idea that is worth considering. It fits well with the consistent
>use of the other C like operators as "||" and "&&" and the disposal of
>"or".
>> Physical reference equality should be used rather sparingly anyways so
>> it is better perhaps that it not even be infix.
>
>I've seen somewhere the operator "===" for physical equality, infix
>obviously. It's not really diffused but seems to me that is really
>intuitive.
I guess it was ruby.
If we are at changes:
I really dislikes the do { } notation.
My suggestion is to use do end pairs, which is borrowed also from ruby.
And if we want more ruby-ish (ada-like?), the matching can be
match a with
| 0 ->
| n ->
end
And end is already a keyword, so it doesn't pollute the namespace, and
the square bracket will remain to the lists.
BTW who cares about the keywords used by the language? Rather to use one
more keyword, than to use weird syntax...
((( this one is not so important
If we are at lists, the current syntax is between sml and prolog:
1) sml uses head::tail, so the :: operator is common
2) prolog uses [Head|Tail], so requiring bracket is common
So, "closing more structures" idea is closer to the prolog syntax, one
could use it, ok, | is used in other contexts, so it couldn't be a too
good idea.
)))
I think this many changes is enough to release a new version with == and
=== included :-)
Gergo
+-[Kontra, Gergely @ Budapest University of Technology and Economics]-+
| Email: kgergely@mcl.hu, kgergely@turul.eet.bme.hu |
| URL: turul.eet.bme.hu/~kgergely Mobile: (+36 20) 356 9656 |
+-------"Olyan langesz vagyok, hogy poroltoval kellene jarnom!"-------+
.
Magyar php mirror es magyar php dokumentacio: http://hu.php.net
-------------------
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
next prev parent reply other threads:[~2002-10-28 8:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 19:02 brogoff
2002-10-25 19:25 ` Oleg
2002-10-26 9:27 ` Stefano Zacchiroli
2002-10-26 11:19 ` Daniel de Rauglaudre
2002-10-26 17:38 ` David Brown
2002-10-26 19:27 ` brogoff
2002-10-28 8:38 ` Kontra, Gergely [this message]
2002-10-28 9:28 ` Oleg
2002-10-28 9:41 ` Florian Douetteau
2002-10-28 10:04 ` Stefano Zacchiroli
2002-10-28 12:20 ` Daniel de Rauglaudre
2002-10-28 16:53 ` brogoff
2002-10-28 16:56 ` Alexander V.Voinov
2002-10-29 18:15 ` Gérard Huet
2002-10-29 18:47 ` Alexander V.Voinov
2002-10-29 20:53 ` Damien Doligez
2002-10-29 21:30 ` M E Leypold @ labnet
2002-10-29 21:42 ` brogoff
2002-10-29 11:30 ` Pierre Weis
2002-10-29 16:48 ` brogoff
2002-10-29 17:20 ` Alessandro Baretta
2002-10-30 17:49 Arturo Borquez
2002-10-31 9:21 ` Daniel de Rauglaudre
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=Pine.LNX.4.21.0210280927120.26219-100000@mlabdial.hit.bme.hu \
--to=kgergely@mlabdial.hit.bme.hu \
--cc=caml-list@inria.fr \
--cc=zack@cs.unibo.it \
/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