From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Gabriel Kerneis <gabriel@kerneis.info>
Cc: Alain Frisch <alain@frisch.fr>,
Jeremie Dimino <jdimino@janestreet.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Extending Format strings
Date: Wed, 2 Jul 2014 15:34:50 +0200 [thread overview]
Message-ID: <CAPFanBH5q8wsYuNSOUud3bta4TfEEpoX09eEzGVH6M-hrGCWgg@mail.gmail.com> (raw)
In-Reply-To: <20140702092706.GB4470@kerneis.info>
> (I'm a little nervous when it comes to using internal compiler libs)
As you should be: there is no guarantee of forward-compatibility of
the format GADTs -- in fact there is a strong confidence of
*non*-compatibility with 4.03.
On Wed, Jul 2, 2014 at 11:27 AM, Gabriel Kerneis <gabriel@kerneis.info> wrote:
> Alain, Jérémie,
>
> On Tue, Jul 01, 2014 at 06:06:44PM +0200, Alain Frisch wrote:
>> We had a very similar issue with some internal LexiFi library, also
>> using @-markers, and returning some structured document. Jeremie's
>> suggestion works very well.
>
> Many thanks for your insights. I'll probably not update CIL code in the
> short term, for backwards-compatibility reasons (I'm a little nervous
> when it comes to using internal compiler libs), but it's nice to see it
> can be done more cleanly than the current implementation.
>
> Best,
> --
> Gabriel
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2014-07-02 13:35 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
2014-07-01 16:06 ` Alain Frisch
2014-07-02 9:27 ` Gabriel Kerneis
2014-07-02 13:34 ` Gabriel Scherer [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=CAPFanBH5q8wsYuNSOUud3bta4TfEEpoX09eEzGVH6M-hrGCWgg@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=gabriel@kerneis.info \
--cc=jdimino@janestreet.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;
as well as URLs for NNTP newsgroup(s).