From: bob zhang <bobzhang1988@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Sexplib bug report
Date: Thu, 16 Feb 2012 20:55:51 -0500 [thread overview]
Message-ID: <CANcqPu6wm+RypDmOAoeyYS9d+kxHRiBP0b9qRU7PMGP4j5DUPQ@mail.gmail.com> (raw)
Hi, I did not find sexplib mailing list, so I posted it here.
sexplib is not compatible with camlp4of
For example
camlp4of Pa_type_conv.cma pa_sexp_conv.cma -str "type ('a,'b) delta =
('b * 'a) "
broken
camlp4o Pa_type_conv.cma pa_sexp_conv.cma -str "type ('a,'b) delta =
('b * 'a) "
good
camlp4of Pa_type_conv.cma pa_sexp_conv.cma -str "type ('a,'b) delta =
('b * 'a) with sexp "
good
camlp4o Pa_type_conv.cma pa_sexp_conv.cma -str "type ('a,'b) delta =
('b * 'a) with sexp "
good
Is it possible to separate the syntax extension from the code
generation part? syntax extension is always fragile, code generation
API is still pretty useful. In my opinion, the main meat lies in code
generation part.
<:sexp< type t = bla bla >> maybe more robust, but it requires
camlp4of as the basic preprocessor instead of camlp4o
--
Best, bob
next reply other threads:[~2012-02-17 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 1:55 bob zhang [this message]
2012-02-17 5:34 ` Markus Mottl
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=CANcqPu6wm+RypDmOAoeyYS9d+kxHRiBP0b9qRU7PMGP4j5DUPQ@mail.gmail.com \
--to=bobzhang1988@gmail.com \
--cc=caml-list@inria.fr \
/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