It looks like it'll be quite difficult to maintain OCaml 4.01 compatibility simultaneously with OCaml 4.02. I took a look at doing this for Conduit, and ended up with this situation:
- 0.10.0 depends on sexplib.syntax (the old camlp4 package), so the metadata for this has been fixed up in OPAM. - 0.11dev is ported to pa_sexp_conv (the new camlp4 package in latest Core), but this is only available on 4.02+. It also introduces an API change in Async_ssl thanks to the max_pending_connection argument disappearing. - 0.11dev could also thus be ported to use ppx directly, since it is now 4.02-only. We have the option of making a pa_sexp_conv package available for 4.01 and compatibility, or just forge forward to jump the camlp4/ppx chasm and make everything use PPX. I'd strongly advocate for the latter (4.02-only support moving forward), since 4.03 is just around the corner. Any strong objections to dropping 4.01 support in Mirage libraries to allow us to take advantage of PPX and drop camlp4? Anil _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
