From: Brian Hurt <bhurt@spnz.org>
To: Jon Harrop <jon@jdh30.plus.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] CFG's and OCaml
Date: Sat, 14 Aug 2004 15:55:03 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0408141548490.4282-100000@localhost.localdomain> (raw)
In-Reply-To: <200408142119.11234.jon@jdh30.plus.com>
On Sat, 14 Aug 2004, Jon Harrop wrote:
> On Saturday 14 August 2004 04:33, Brian Hurt wrote:
> > > 3. If so, is the fact that most languages disallow "a<b<c" due to this?
> >
> > No. "a<b<c" is parsed the same way as "a+b+c".
>
> Sorry, I should have been more specific. With left- or right- or
> non-associative, commuting, 'a->'a->'a operators (like + and *) you can get
> away with parsing that way, e.g. "a+b+c" as:
>
> either (a+b)+c or a+(b+c)
>
> But you can't do this with comparison 'a->'a->bool operators because it forces
> you to deviate from conventional mathematical meaning, e.g. you get a type
> error in OCaml on the "3" in "1<2<3" because it parses as "(1<2)<3" which
> evaluates to "true<3" which just doesn't make any sense.
>
The syntax of a language doesn't enforce a given meaning on the language
being parsed. "Colorless green ideas sleep furiously" is a syntactically
correct English sentence, even if it is utterly meaningless.
The AST of a<b<c has to be one of two ways:
< <
/ \ / \
a < or < c
/ \ / \
b c a b
i.e. a < (b < c) or (a < b) < c. What the meaning of these two
expressions are is entirely up to the compiler- more spefically, up to the
parts which are not lex or yacc based.
Although this does bring up one interesting question- is a<b<c
syntactically different than (a<b)<c? Generally, languages want to
consider "extra" parenthesis to be harmless.
--
"Usenet is like a herd of performing elephants with diarrhea -- massive,
difficult to redirect, awe-inspiring, entertaining, and a source of
mind-boggling amounts of excrement when you least expect it."
- Gene Spafford
Brian
-------------------
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:[~2004-08-14 20:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 14:04 David McClain
2004-08-13 15:05 ` Damien Doligez
2004-08-13 15:26 ` David McClain
2004-08-13 16:12 ` Damien Doligez
2004-08-13 15:28 ` David McClain
2004-08-13 15:49 ` Brian Hurt
2004-08-13 16:04 ` David McClain
2004-08-13 16:29 ` Brian Hurt
2004-08-13 16:42 ` Xavier Leroy
2004-08-13 17:18 ` Ken Rose
2004-08-13 18:55 ` Brian Hurt
2004-08-14 0:25 ` Jon Harrop
2004-08-14 0:57 ` Erik de Castro Lopo
2004-08-14 8:52 ` Alan Schmitt
2004-08-14 3:33 ` Brian Hurt
2004-08-14 7:55 ` skaller
2004-08-14 20:19 ` Jon Harrop
2004-08-14 20:55 ` Brian Hurt [this message]
2004-08-14 20:57 ` Marcin 'Qrczak' Kowalczyk
2004-08-14 22:15 ` skaller
2004-08-15 1:26 ` Jon Harrop
2004-08-15 8:24 ` skaller
2004-08-15 15:39 ` Brian Hurt
2004-08-15 16:54 ` Jon Harrop
2004-08-14 22:13 ` skaller
2004-08-13 16:58 ` Paul Snively
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 19:15 David McClain
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.44.0408141548490.4282-100000@localhost.localdomain \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=jon@jdh30.plus.com \
/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