From: Markus Mottl <markus.mottl@gmail.com>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Newest Sexplib and Hashtbl
Date: Sun, 18 Sep 2011 14:53:53 -0400 [thread overview]
Message-ID: <CAP_800qz36ZNhzJpUbOAbFr6+kBBPiARmfEfmXdQoqaMit+E6g@mail.gmail.com> (raw)
In-Reply-To: <1316371281.68127.YahooMailNeo@web111512.mail.gq1.yahoo.com>
Hi,
There have been some changes to the newest release of Sexplib. It is
now required to open "Sexplib.Std" to "see" the default converters for
the standard OCaml types. The same is true for bin-prot.
The code automatically generated by the preprocessor used to hard-code
the converters by explicitly referring to the functions in Sexplib.
But this prevented users from overriding them, motivating Jane Street
to propose this change.
Sorry, it seems that this change hasn't been mentioned in the docs.
This will be fixed in future documentation releases. Please let me
know if there are any other issues.
Regards,
Markus
On Sun, Sep 18, 2011 at 14:41, Dario Teixeira <darioteixeira@yahoo.com> wrote:
> Hi,
> I've updated to the latest version of Sexplib, and the support for hashtable
> serialisation
> seems broken or at least changed. I was accustomed to using the syntax
> extension
> for convenient declaration of (de)serialisers, and this worked too for the
> Hashtbl module.
> For example:
>
> type dict_t = (key_t, value_t) Hashtbl.t with sexp
> But with Sexplib 7.0.4 this produces an error:
>
> Error: Unbound value Hashtbl.t_of_sexp
> Is this a bug, or must the (de)serialisers be declared manually with the
> newer versions
> of Sexplib?
> Thanks in advance for your time!
> Best regards,
> Dario Teixeira
>
--
Markus Mottl http://www.ocaml.info markus.mottl@gmail.com
prev parent reply other threads:[~2011-09-18 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 18:41 Dario Teixeira
2011-09-18 18:53 ` Markus Mottl [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=CAP_800qz36ZNhzJpUbOAbFr6+kBBPiARmfEfmXdQoqaMit+E6g@mail.gmail.com \
--to=markus.mottl@gmail.com \
--cc=caml-list@inria.fr \
--cc=darioteixeira@yahoo.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).