From: David Teller <David.Teller@ens-lyon.org>
To: "Michaël Grünewald" <michael.grunewald@laposte.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Automatically install printer
Date: Fri, 15 Jun 2007 16:25:27 +0200 [thread overview]
Message-ID: <1181917527.14726.28.camel@Blefuscu> (raw)
In-Reply-To: <hjlkemg1oc.fsf@darboux.math.univ-montp2.fr>
I concur that this would be nice.
Cheers,
David
On Thu, 2007-06-14 at 14:28 +0200, Michaël Grünewald wrote:
> Hi all,
>
> the toplevel `ocaml' allows to install printers for custom types
> with the `#install_printer' directive. Is this possible to do this
> automatically?
>
> Being more precise, if I define module `F' made of a type `t' and a
> `to_string' function, can I arrange so that the toplevel uses function
> `F.to_string' to print `F.t' values? I can use a wrapper script around
> the `ocaml' command that will issue the directive before giving back the
> hand, but this would break if `F' happens to be a functor: only the
> functor instantiation knows what the correct directive is.
prev parent reply other threads:[~2007-06-15 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 12:28 Michaël Grünewald
2007-06-15 14:25 ` David Teller [this message]
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=1181917527.14726.28.camel@Blefuscu \
--to=david.teller@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=michael.grunewald@laposte.net \
/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).