Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Coccinelle and the Dumper module
Date: Tue, 23 Feb 2016 14:10:16 +0100	[thread overview]
Message-ID: <20160223131016.GA15598@pl-59055.rocqadm.inria.fr> (raw)
In-Reply-To: <CAPFanBECvX097j8_b+WL2jSkB4Wx0c8UK_9+RX8Ho6AzHRqBYg@mail.gmail.com>

Thanks a lot for your feedback, Gabriel!

Sébastien.

Gabriel Scherer (2016/02/23 06:46 -0500):
> This "dump" code has lived on in Extlib (to which Richard
> participated, I believe), and is also part of Batteries. I know that
> ygrek, Extlib's current maintainers, has done some fixes to it (I
> think we ported them into Batteries), so you may want to look there.
> 
> On Tue, Feb 23, 2016 at 6:05 AM, Sébastien Hinderer
> <Sebastien.Hinderer@inria.fr> wrote:
> > Dear Richard,
> >
> > Thanks a lot for your prompt, positive and helpful respnse!
> >
> >> Yes.  I'm not sure if it was ever licensed properly, but I'm willing
> >> now to (re?)license it under a liberal 3 clause, no advertising
> >> requirement, BSD license:
> >>
> >>   https://fedoraproject.org/wiki/Licensing:BSD?rd=Licensing/BSD#New_BSD_.28no_advertising.2C_3_clause.29
> >>
> >> This is pretty close to "do what you like with it".  I'm CC-ing this
> >> to caml-list to put this in the public record.
> >
> > Great! Thanks!
> >
> >> > Is there a more recent version of the code available?
> >>
> >> Not as far as I know, but if you search for "dumper.mli" you will see
> >> many copies in different places, so I suppose you'll have to go check
> >> if people have added useful features that you want.
> >
> > Okay. I think we are fine with what we have, at the moment.
> >
> > So there were two warnings, one about an unused "open Printf" and one
> > about an unused variable.
> >
> > The attached version of the module fixes them.
> >
> > I may also get rid of the "open Obj" statement and qualify all the
> > references to this module as I fnd this style more clear.
> >
> > Cheers,
> > Sébastien.
> >

      parent reply	other threads:[~2016-02-23 13:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160223095607.GA10534@pl-59055.rocqadm.inria.fr>
2016-02-23 10:33 ` Richard W.M. Jones
2016-02-23 11:05   ` Sébastien Hinderer
2016-02-23 11:46     ` Gabriel Scherer
2016-02-23 12:02       ` Richard W.M. Jones
2016-02-23 13:10       ` Sébastien Hinderer [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=20160223131016.GA15598@pl-59055.rocqadm.inria.fr \
    --to=sebastien.hinderer@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=rjones@redhat.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