caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alex Baretta <alex@baretta.com>
To: Mikael Brockman <phubuh@phubuh.org>, ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Typechecking madness
Date: Thu, 04 Mar 2004 12:48:14 +0100	[thread overview]
Message-ID: <4047177E.70802@baretta.com> (raw)
In-Reply-To: <87llmiyn4g.fsf@authorize.quake3arena.com>

Mikael Brockman wrote:
> Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp> writes:
> 
> 
>>From: Alex Baretta <alex@baretta.com>

>>>This expression has type
>>>   'a. (('a Pxp_document.node #Pxp_document.extension as 'a) -> unit) -> 
>>>unit
>>>but is here used with type
>>>   'b. (('b Pxp_document.node #Pxp_document.extension as 'b) -> unit) -> 
>>>unit

>>Even if the type checking is correct in detecting a type error, this
>>is not a valid error message.
> 
> 
> Actually, the first expert FAQ [1] addresses a (valid) such error
> message.  Briefly, this kind of error occurs when you have defined two
> types with the same name, which is easy to do when you're using the
> REPL.
> 

Allow me to point out that I was not using the toplevel (REPL, as you 
call it); rather I was compiling a PXP document transformation with the 
toplevel. There actually was a type error in my code, and I did manage 
to figure it out. The error message did not really help, though.

Alex

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2004-03-04 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-01 14:18 Alex Baretta
2004-03-03  8:16 ` Jacques Garrigue
2004-03-03 15:19   ` Mikael Brockman
2004-03-04 11:48     ` Alex Baretta [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=4047177E.70802@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=phubuh@phubuh.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).