From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: Upgrading sexplib-2.7.0 to camlp4 3.10
Date: Tue, 1 May 2007 17:49:14 +0200 [thread overview]
Message-ID: <cd67f63a0705010849r6a2bd1dfj8fae7a69f8b561c3@mail.gmail.com> (raw)
In-Reply-To: <E7DDAE68-16A0-4CE9-8195-93DEE34405A3@gmail.com>
On 5/1/07, Joel Reymont <joelr1@gmail.com> wrote:
> Moving on! I hope this long thread will be instructive for later
> Google searches.
>
> (* Get the path associated with a polymorphic type *)
> let rec get_appl_path _loc = function
> | <:ctyp< $lid:_$ >> as tp -> tp
> | <:ctyp< $_$ . $_$ >> as tp -> tp
> | <:ctyp< $tp$ $_$ >> -> get_appl_path _loc tp
> | _ -> failwith "get_appl_path: unknown type"
>
> File "pa_sexp_conv.ml", line 320, characters 22-25:
> While expanding quotation "ctyp" in a position of "patt":
> Parse error: ident_of_ctyp: this type is not an identifier
>
> That would be <:ctyp< $_$ . $_$ >> as tp -> tp
>
> It would work (from what I understand) if it was <:ctyp< ! $_$ . $_$
> >> but what does this match and how to fix it?
>
> Thanks, Joel
>
No there is a difference between <:ctyp< ! 'a ... 'z . typ >> and
<:ctyp< id1.id2 >> the first one means forall, the second one is the
access of the `id2' field of the module `id1'.
The goal the function get_appl_path is to get the type constructor, so
go down left into all type applications.
Reminder, type application depends on the syntax:
original syntax: int list, (string, int list) Hashtbl.t
revised syntax: list int, Hashtbl.t string (list int)
If I well remember, you use camlp4of, so that's the original syntax.
Then you should go right in application nodes: <:ctyp< $_$ $t$ >>.
let rec get_appl_path _loc = function
| <:ctyp< $id:i$ >> -> i
| <:ctyp< $_$ $tp$ >> -> get_appl_path _loc tp
| _ -> failwith "get_appl_path: unknown type"
--
Nicolas Pouillard
next prev parent reply other threads:[~2007-05-01 15:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 13:55 Joel Reymont
2007-04-30 14:01 ` Nicolas Pouillard
2007-04-30 14:07 ` Joel Reymont
2007-04-30 14:17 ` Nicolas Pouillard
2007-04-30 14:31 ` Joel Reymont
2007-04-30 14:46 ` Joel Reymont
2007-04-30 15:19 ` Nicolas Pouillard
2007-04-30 15:29 ` Joel Reymont
2007-04-30 15:46 ` Nicolas Pouillard
2007-04-30 19:44 ` Joel Reymont
2007-04-30 21:08 ` Joel Reymont
2007-05-01 7:20 ` Nicolas Pouillard
2007-05-01 13:21 ` Joel Reymont
2007-05-01 13:35 ` Nicolas Pouillard
2007-05-01 13:54 ` Joel Reymont
2007-05-01 14:16 ` Nicolas Pouillard
2007-05-01 14:31 ` Joel Reymont
2007-05-01 15:49 ` Nicolas Pouillard [this message]
2007-05-01 16:14 ` Joel Reymont
2007-05-01 16:27 ` Nicolas Pouillard
2007-05-01 16:35 ` Joel Reymont
2007-05-01 16:39 ` Nicolas Pouillard
2007-05-01 16:50 ` Joel Reymont
2007-05-01 17:13 ` Nicolas Pouillard
2007-05-01 17:04 ` camlp4 3.10: Matching variant types Joel Reymont
2007-05-03 5:58 ` [Caml-list] " Dmitry Bely
2007-05-01 16:05 ` Upgrading sexplib-2.7.0 to camlp4 3.10 Joel Reymont
2007-05-01 16:19 ` Nicolas Pouillard
2007-04-30 21:16 ` Joel Reymont
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=cd67f63a0705010849r6a2bd1dfj8fae7a69f8b561c3@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=joelr1@gmail.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