From: Virgile Prevosto <virgile.prevosto@m4x.org>
To: OCAML <caml-list@inria.fr>
Subject: [Caml-list] ocamldoc type-checking error
Date: Fri, 4 Jan 2013 18:29:12 +0100 [thread overview]
Message-ID: <CA+yPOVg0eTv0Kah_dHVnuwE1Ofk1-C1LAjDPdmN_ZYL=OuhMqg@mail.gmail.com> (raw)
Hello list,
I have some trouble compiling the API documentation of a fairly large
project with ocamldoc. Unfortunately, I did not succeed in reproducing
the issue on a reduced example. Here are the symptoms:
- The command line is ocamldoc -I ... ... a.ml b.ml ... It fails with
an error message saying
File "b.ml", line 91, characters 58-60:
Error: This expression has type
Foo.t = Bar.t
but an expression was expected of type Baz.t
Baz.t being another synonym of Bar.t
- if you reverse a.ml and b.ml on the command line, everything works
fine (a.ml and b.ml are independent from each other, although they
share some common dependencies, in particular Foo, Bar and Baz)
- it only appears on OCaml 4.00.0 and 4.00.1: 3.12.1 is fine
As there is a workaround, solving this issue is not really urgent, but
I'd like to know if someone has a clue on how to investigate further.
Best regards,
--
E tutto per oggi, a la prossima volta
Virgile
reply other threads:[~2013-01-04 17:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+yPOVg0eTv0Kah_dHVnuwE1Ofk1-C1LAjDPdmN_ZYL=OuhMqg@mail.gmail.com' \
--to=virgile.prevosto@m4x.org \
--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