From: Brian Rogoff <bpr@best.com>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: SooHyoung Oh <shoh@duonix.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] function vs. parser
Date: Thu, 13 Sep 2001 07:13:16 -0700 (PDT) [thread overview]
Message-ID: <20010913070823.C3927-100000@shell5.ba.best.com> (raw)
In-Reply-To: <20010913104853.M24601@verdot.inria.fr>
On Thu, 13 Sep 2001, Daniel de Rauglaudre wrote:
> On Thu, Sep 13, 2001 at 05:20:11PM +0900, SooHyoung Oh wrote:
>
> > Could anyone explain me why "parser" was introduced in Ocaml?
> > As you know, "function" is using in the caml light-instead of "parser".
> > "parser" must be a reserved word like "let" and "function", right?
>
> Right: "parser" is used because they are not functions. In Caml Light,
> we used "function", but it was an bad idea: the pattern matching rules
> in parsers have nothing to do with the pattern matching rules in
> functions and it was important to separate the notions.
I have a petty complaint. Another name would have been better, say "parse"
to match "match" since "parser" is a good name for a type and at least in
English there are no good synonyms. If you start writing combinator
parsers you have to hack the keyword parser to be parser_t or _parser or
somesuch, which is a little ugly.
Hey, I said it is a *petty* complaint! ;-)
-- Brian
-------------------
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 prev parent reply other threads:[~2001-09-13 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 8:20 SooHyoung Oh
2001-09-13 8:48 ` Daniel de Rauglaudre
2001-09-13 14:13 ` Brian Rogoff [this message]
2001-09-13 16:09 ` Daniel de Rauglaudre
2001-09-13 16:50 ` Brian Rogoff
2001-09-13 16:51 ` Pierre Weis
2001-09-13 18:09 Krishnaswami, Neel
2001-09-13 20:55 ` Brian Rogoff
2001-09-13 21:49 Krishnaswami, Neel
2001-09-14 12:50 ` Gerd Stolpmann
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=20010913070823.C3927-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@inria.fr \
--cc=shoh@duonix.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;
as well as URLs for NNTP newsgroup(s).