From: "Kim Nguyễn" <Kim.Nguyen@lri.fr>
To: "Richard W.M. Jones" <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bug in camlp4 4.02 ? [ was: cduce on ocaml 4.02 ]
Date: Fri, 1 Aug 2014 13:03:19 +0200 [thread overview]
Message-ID: <CAJCP7wGPE1CotCXCXebxAGcCibJyqQ82LOeO9W0+0QANhSjTug@mail.gmail.com> (raw)
Hi Richard, hi everyone,
On Thu, Jul 31, 2014 at 4:21 PM, Richard W.M. Jones <rich@annexia.org> wrote:
>
> I wonder if anyone has managed to compile cduce with OCaml 4.02?
>
> Currently it fails at:
>
> File "parser/parser.ml", line 2, characters 0-6:
> Error: Unbound constructor Ulexer
note: for me it "fails" (I kill ocamlopt) before because of a long
forgotten -inline 10000 that makes ocaml generate a large ( >90 MB .s
file on which "as" takes a lot of time, for typing/typer.ml), putting
a saner -inline 100 in Makefile.distribg makes the file compile and I
can stumble on the same camlp4 issue:
> The post-preprocessor code looks very wrong to me:
>
> let _ = Ulexer ## generated from input "open Ulexer"
>
> let tloc (i, j) = (i, (* let raise = Pervasives.raise *) j)
>
> let nopos = ((-1), (-1))
>
> It could be a bug in camlp4?
The following test cases exhibit the problematic behavior of camlp4 (I
don't know if it's just an intended change in behaviour or a bug, I
don't mind filling a bug report in the latter case):
bug1.ml -----------------------
#load "pa_extend.cmo";;
open A
open B
open C
open D
open E
bug2.ml -----------------------
#load "pa_extend.cmo";;
open A
open B
open C
open D
open E
open F
$ camlp4 -version
4.02.0+dev12-2014-07-30
$ camlp4o bug1.ml
E
$ camlp4o bug2.ml
let _ = E
open F
Note that if I don't go until "open E" the output file is empty
with camlp4 from ocaml 4.01.0, everything works as expected (that is
the #load is absent from the output, and all the open A...F are
present in the output).
Cheers,
--
Kim
next reply other threads:[~2014-08-01 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 11:03 Kim Nguyễn [this message]
2014-08-01 14:12 ` Richard W.M. Jones
2014-08-01 15:11 ` Jeremie Dimino
2014-08-01 16:31 ` Kim Nguyễn
2014-08-02 12:35 ` Richard W.M. Jones
2014-08-02 13:11 ` Kim Nguyễn
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=CAJCP7wGPE1CotCXCXebxAGcCibJyqQ82LOeO9W0+0QANhSjTug@mail.gmail.com \
--to=kim.nguyen@lri.fr \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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).