From: Leo White <leo@lpw25.net>
To: "Ömer Sinan Ağacan" <omeragacan@gmail.com>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Problems with printing MetaOCaml generated code
Date: Fri, 01 May 2015 12:45:07 -0400 [thread overview]
Message-ID: <1430498707.1164081.261525093.47AD6B00@webmail.messagingengine.com> (raw)
In-Reply-To: <CAMQQO3n1Uw_fNN0kdGtwscRLWqtafOVTz2zkjL6rW66vOGBBxg@mail.gmail.com>
On Fri, 1 May 2015, at 12:41 PM, Ömer Sinan Ağacan wrote:
> 2015-05-01 12:16 GMT-04:00 Leo White <leo@lpw25.net>:
> > From a quick look at the code, it seems pretty clear that `eval_ref` is not serializable.
> > It is a local function so there is no AST fragment which could represent it globally. I
> > suspect that if you moved `eval_ref` into a separate module, so that it was
> > a global function, then this code would work.
>
> It should serialize `p'`, not `eval_ref`, I'd expect serialization of
> `eval_ref` to be the identifier `eval_ref`.
You can't serialize `eval_ref` as `eval_ref` because that is a local identifier. If you print
out `eval_ref` into some other ml file and compiler it, it is going to give an "Unbound
identifier eval_ref" error.
Regards,
Leo
next prev parent reply other threads:[~2015-05-01 16:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 18:36 Ömer Sinan Ağacan
2015-04-30 19:52 ` Jacques Carette
2015-04-30 20:25 ` Ömer Sinan Ağacan
2015-04-30 20:57 ` Ömer Sinan Ağacan
2015-04-30 21:35 ` Jeremy Yallop
2015-05-01 11:21 ` oleg
2015-05-01 14:34 ` Ömer Sinan Ağacan
2015-05-01 16:16 ` Leo White
2015-05-01 16:41 ` Ömer Sinan Ağacan
2015-05-01 16:45 ` Leo White [this message]
2015-05-01 16:53 ` Ömer Sinan Ağacan
2015-05-02 18:45 ` Ömer Sinan Ağacan
2015-05-02 20:49 ` Jacques Carette
2015-05-03 1:56 ` Ömer Sinan Ağacan
2015-05-03 2:28 ` Jacques Carette
2015-05-03 3:19 ` Ömer Sinan Ağacan
2015-05-03 8:40 ` Gabriel Scherer
2015-05-03 14:28 ` Ömer Sinan Ağacan
2015-05-03 15:24 ` Leo White
2015-05-03 15:50 ` Ömer Sinan Ağacan
2015-05-06 9:50 ` oleg
2015-05-06 15:58 ` Jeremy Yallop
2015-05-06 16:45 ` Yotam Barnoy
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=1430498707.1164081.261525093.47AD6B00@webmail.messagingengine.com \
--to=leo@lpw25.net \
--cc=caml-list@inria.fr \
--cc=omeragacan@gmail.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