From: Pierre Weis <weis@pauillac.inria.fr>
To: Michael.Jones@cl.cam.ac.uk (Michael Jones)
Cc: caml-list@pauillac.inria.fr
Subject: Re: Perplexing type error.
Date: Wed, 12 Jun 1996 20:42:09 +0200 (MET DST) [thread overview]
Message-ID: <199606121842.UAA19982@pauillac.inria.fr> (raw)
In-Reply-To: <E0uTnCw-00060C-00@heaton.cl.cam.ac.uk> from "Michael Jones" at Jun 12, 96 11:31:25 am
> Tres petit(e) abstract en Francais:
> Il y a une "type error" que je ne comprende pas.
Le proble`me est bien connu et re'fe'rence' dans la FAQ. Regardez dans
http://pauillac.inria.fr/caml/FAQ/FAQ_EXPERT-fra.html, la premie`re
question sur le typage, qui s'intitule
<<Un type est incompatible avec lui-même ?>>
et doit re'pondre a` votre question. J'en extrais la conclusion:
La solution: quitter la session et tout recharger dans une nouvelle
session. Si le phénomène apparaît lors de la compilation d'un fichier,
il faut recompiler tous les fichiers dont il dépend.
J'espe`re que ca marchera pour vous.
> While [...]
>
> This expression has type lexcode list -> preterm * lexcode list,
> but is used with type lexcode list -> preterm * lexcode list.
[...]
This is a well-known pitfall of ML, it is referenced in the Caml
FAQ. Have a look at
http://pauillac.inria.fr/caml/FAQ/FAQ_EXPERT-eng.html, the first
question about type checking is
<<Error message: a type is not compatible with itself ?>>
it should answer to your question. The conclusion given here is:
Solution: quit your interactive system and reload your files in a new
session. If it appears when compiling a file, you have to recompile
all the files that your file depends upon.
Hope this helps,
Pierre Weis
INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis
prev parent reply other threads:[~1996-06-12 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-12 9:31 Michael Jones
1996-06-12 18:42 ` Pierre Weis [this message]
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=199606121842.UAA19982@pauillac.inria.fr \
--to=weis@pauillac.inria.fr \
--cc=Michael.Jones@cl.cam.ac.uk \
--cc=caml-list@pauillac.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