From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] function vs. parser
Date: Thu, 13 Sep 2001 18:09:19 +0200 [thread overview]
Message-ID: <20010913180919.B30967@verdot.inria.fr> (raw)
In-Reply-To: <20010913070823.C3927-100000@shell5.ba.best.com>; from bpr@best.com on Thu, Sep 13, 2001 at 07:13:16AM -0700
Hi,
> I have a petty complaint. Another name would have been better, say "parse"
> to match "match"
But "parser" is like "function", not like "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.
Same problem with "type": in my parsers, I would like to have "expr",
"patt" and "type". I named it "ctyp", ugly too. And "constraint"...
which is named "constrain" in the OCaml parser. It has been the
problem with keywords since the Pascal language...
> Hey, I said it is a *petty* complaint! ;-)
Well, there is some syntactic preprocessor for OCaml - I don't
remember the name - which can do that...
--
Daniel de RAUGLAUDRE
daniel.de_rauglaudre@inria.fr
http://cristal.inria.fr/~ddr/
-------------------
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 16:09 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
2001-09-13 16:09 ` Daniel de Rauglaudre [this message]
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=20010913180919.B30967@verdot.inria.fr \
--to=daniel.de_rauglaudre@inria.fr \
--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).