From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Camlp4: generating printers of types
Date: Tue, 10 Dec 2002 18:38:19 +0100 [thread overview]
Message-ID: <20021210183819.H4933@verdot.inria.fr> (raw)
In-Reply-To: <3DF60943.B9E543AB@earthlink.net>; from kenarose@earthlink.net on Tue, Dec 10, 2002 at 07:33:23AM -0800
Hi,
On Tue, Dec 10, 2002 at 07:33:23AM -0800, Ken Rose wrote:
> and so on into gen_print_type. Or do I not understand what $uid:x$
> does?
If x is a string <:expr< $uid:x$ >> produces "the uppercase identifier
named by the value of x". If x is "Foo", this produces the identifier
Foo. Notice that it works even if x does not contain an uppercase
identifier: OCaml with interpret it as a module name or as a
constructor name (depending on its position), whatever its value.
Sorry, for your Baz.Baz.t, you need your <:ctyp< $uid:m2$.$uid:m$.$lid:s$ >>
The better is to use an iterator, or use the recursion to treat the
general case.
> > In Revised syntax, they are like in normal syntax, but the parentheses
> > are compulsory.
>
> Here, I want to match
> type t = int * int
> within gen_one_print_fun, to produce a printer instead of "failwith...".
In Normal syntax, you can write "int * int" but inside the predefined
quotations of AST, you have to use the Revised syntax. See the chapter
about it in the reference manual.
You must write it <:ctyp< (int * int) >>. And if tl is a list of ctyp,
you can obtain the type tuple of this list of types with:
<:ctyp< ($list:tl$) >>
See the chapter about AST quotations.
> > This message of OCaml just means that there are syntactic restrictions
> > of the "let rec". In this case, you should produce either a "let" without
> > "rec" or, an eta extension: "let rec print_t x = print_int x".
>
> I'd suspected that, though I'm still curious as to why that's so.
Damien Doligez answered you on that point; this is typing and
therefore not the work of Camlp4.
> Still, what I really want is a generally useful tool to produce these
> useful functions, without having to spend too much time right now
> learning camlp4. It's for my regular work, where I'm building a
> compiler for a DSL. I don't understand camlp4 well enough to know how
> to suppress the "rec", and I'm hoping to avoid learning, at least for a
> while. It's a great tool, but I have only so much time.
Well, if you don't have time to look at it, I can help.
--
Daniel de RAUGLAUDRE
http://cristal.inria.fr/~ddr/
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-12-10 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 13:13 Daniel de Rauglaudre
2002-10-09 17:18 ` Markus Mottl
2002-10-25 19:20 ` Ken Rose
2002-10-25 20:02 ` Chris Hecker
2002-10-26 0:11 ` Daniel de Rauglaudre
2002-12-10 2:01 ` Ken Rose
2002-12-10 12:25 ` Daniel de Rauglaudre
2002-12-10 15:33 ` Ken Rose
2002-12-10 17:38 ` Daniel de Rauglaudre [this message]
2002-12-10 13:20 ` Damien Doligez
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=20021210183819.H4933@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