caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jeremie Dimino <jdimino@janestreet.com>
To: Gabriel Kerneis <gabriel@kerneis.info>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Extending Format strings
Date: Tue, 1 Jul 2014 16:27:09 +0100	[thread overview]
Message-ID: <CANhEzE4_gCgRRVNE+VCLhYwhvy-dpR3xwb8Yi4CyirZ1oWxR1g@mail.gmail.com> (raw)
In-Reply-To: <20140701095955.GE4120@kerneis.info>

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Tue, Jul 1, 2014 at 10:59 AM, Gabriel Kerneis <gabriel@kerneis.info>
wrote:

> Dear all,
>
> in CIL <http://cil.sf.net>, the module Pretty provides a Format-like
> interface with a few extensions compared to usual format strings.
> Implementation-wise, it uses string_of_format and re-implements most of
> the logic of the pre-4.02 Format module, with Obj.magic all over the
> place.
>
> I wondered if anyone has done something similar in their own project
> (extending Format in one way or another), and if the new GADT-based
> approach could provide a cleaner solution?
>
> One thing I quite like with the current code, despite its uglyness, is
> its concision. I am right in assuming that switching to GADTs would
> require a lot more boilerplate?
>

I had a quick look at [Pretty.dprintf] and I think you could use
[CamlinternalFormat.make_printf] to implement it with 4.02. @-sequences are
already recognized by the format parser in the compiler, but it should be
compatible with [Pretty]'s syntax, you just have to interpret the
constructors differently. It should actually make the code of
[Pretty.dprintf] much simpler.

-- 
Jeremie

[-- Attachment #2: Type: text/html, Size: 1642 bytes --]

  parent reply	other threads:[~2014-07-01 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01  9:59 Gabriel Kerneis
2014-07-01 14:15 ` Tianyi Cui
2014-07-01 14:39   ` Gabriel Kerneis
2014-07-01 15:27 ` Jeremie Dimino [this message]
2014-07-01 16:06   ` Alain Frisch
2014-07-02  9:27     ` Gabriel Kerneis
2014-07-02 13:34       ` Gabriel Scherer

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=CANhEzE4_gCgRRVNE+VCLhYwhvy-dpR3xwb8Yi4CyirZ1oWxR1g@mail.gmail.com \
    --to=jdimino@janestreet.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel@kerneis.info \
    /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).