Hello, Am Mittwoch, den 18.01.2012, 11:43 +0100 schrieb Stéphane Glondu: > You'll have to be more specific. Do you call string_of_sexp directly > from your code? If so, you are affected by an upstream API change, and > this is merely a porting issue and doesn't qualify as a bug (or, put > differently, is a bug on your side), IMHO. > > By grepping through current sexplib310 source package, I can see there > is a Std.string_of_sexp... did you try that? All stuff is generated throug sexplib-preprocessor for camlp4. The hint from Mehdi Dogguy was helpful, the problem was an undocumented open Sexplib.Std, thanks -- Andreas Romeyke - Abteilung Blindenschrift - Deutsche Zentralbücherei für Blinde zu Leipzig (DZB) Gustav-Adolf-Straße 7, 04105 Leipzig Tel: +49 341 7113-..., Fax: +49 341 7113-125 Internet: www.dzb.de E-Mail: andreas.romeyke@dzb.de
Attachment:
signature.asc
Description: This is a digitally signed message part