From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Caml List" <caml-list@inria.fr>, "Aleksey Nogin" <nogin@metaprl.org>
Subject: Re: [Caml-list] 3.10+beta: Camlp4: AST mapping treats record labels as patterns; should they have type ident instead?
Date: Fri, 20 Apr 2007 17:17:44 +0200 [thread overview]
Message-ID: <cd67f63a0704200817i58fb0537x903bb37ae9b44984@mail.gmail.com> (raw)
In-Reply-To: <462643BD.8050309@metaprl.org>
On 4/18/07, Aleksey Nogin <nogin@metaprl.org> wrote:
> On 18.04.2007 01:11, Nicolas Pouillard wrote:
>
> > Why do you mix the old definition of PaRec with the new definition of
> > ExRec.
[...]
> >
> > For patterns there is something doable:
> >
> > | PaEq of Loc.t and patt and patt (* p = p *)
> > Can become
> > | PaEq of Loc.t and ident and patt (* i = p *)
> >
> > Since that node is only used with an ident on his left.
>
> Yes, this sounds like a good thing to do.
That's now in CVS.
> > For expressions it's more complex
> >
> Is it the same issue as the workaround discussion above - the "proper"
> way to make this distinction would be to introduce a separare
> rec_binding type similar, but separate from the binding one? But is it
> true that the "b; b" case in the binding type is only used for records?
> If so, it would seem that splitting the binding type would not result in
> that much duplication. Of course, I am only starting to understand the
> new setup, no I may be completely wrong here.
Yes it is just used for records and objects {< f1 = e1 ; ... ; fN = eN >}.
But having one more category seems heavy, I have to think more about it.
--
Nicolas Pouillard
next prev parent reply other threads:[~2007-04-20 15:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 17:50 Aleksey Nogin
2007-04-18 8:11 ` [Caml-list] " Nicolas Pouillard
2007-04-18 16:13 ` Aleksey Nogin
2007-04-20 15:17 ` Nicolas Pouillard [this message]
2007-05-03 9:16 ` Nicolas Pouillard
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=cd67f63a0704200817i58fb0537x903bb37ae9b44984@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=nogin@metaprl.org \
/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