From: Manuel Fahndrich <maf@microsoft.com>
To: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: RE: stream pattern [< pat=exp >] and extensions to ordinary patte rn m atching
Date: Fri, 14 May 1999 09:14:34 -0700 [thread overview]
Message-ID: <783D93998201D311B0CF00805FEAA07B7E8DAE@RED-MSG-42> (raw)
I have to reply to my own earlier (faulty) comments...
[...]
I believe that with such an extension to
OCAML, the pattern language we explored in the ICFP paper could be
expressed
completely (and more).
[...]
This is not entirely true. The pattern language explored in the ICFP paper
allows one to write non-deterministic patterns that get influenced by the
context. For example:
pat leftOrRight(x) =
(x, _)
| (_, x)
If I then write
match (1,2) with
leftOrRight(2) ->
| leftOrRight(y) ->
the first clause would apply. Using the pat=exp approach from stream
parsers, such choices in function of pat would not be possible. I consider
this feature not essential, and having pat=exp patterns whose semantics
evaluate exp first without regard to pat would still be very useful.
-Manuel Fahndrich
next reply other threads:[~1999-05-14 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-14 16:14 Manuel Fahndrich [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-05-10 16:12 Don Syme
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=783D93998201D311B0CF00805FEAA07B7E8DAE@RED-MSG-42 \
--to=maf@microsoft.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;
as well as URLs for NNTP newsgroup(s).