From: "Beck01, Wolfgang" <BeckW@t-systems.com>
To: caml-list@inria.fr
Subject: RE: [Caml-list] strange behaviour with variants and "cannot be g eneralized"
Date: Wed, 10 Sep 2003 09:10:06 +0200 [thread overview]
Message-ID: <ADD42C8394EBD4118A3D0003470C18F00950F3D8@G9JJT.mgb01.telekom.de> (raw)
Didier Remy [mailto:remy@morgon.inria.fr] wrote:
> Here is some explanation of
>
> 1) what happened in version 3.06 and
> 2) how this is related to a relaxed form of value restriction,
> 3) which is actually orthogonal to the solution implemented in 3.07
>
> [detailed explanation omitted]
well, I was not aware that compilation of polymorphic variants is an area
of ongoing research. In the OCaml manual, they are not mentioned under
"Language extensions" but as a section in the chapter "An introduction to
Objective Caml". There is a statement
"In programs, polymorphic variants work like usual ones. You just
have to prefix their names with a backquote character `."
and this is not true, at least in 3.06. After spending another evening
with weird type errors, I replaced polymorphic variants with ordinary
ones. My project looks uglier now since I had to split up some files,
but at least it compiles and runs.
--
Wolfgang Beck
-------------------
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
next reply other threads:[~2003-09-10 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 7:10 Beck01, Wolfgang [this message]
2003-09-10 8:12 ` Fernando Alegre
2003-09-10 8:18 ` Jacques Garrigue
2003-09-10 10:39 ` skaller
2003-09-10 9:48 ` skaller
2003-09-10 11:34 ` Frederic De Jaeger
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 14:13 Beck01, Wolfgang
2003-09-09 19:17 ` Didier Remy
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=ADD42C8394EBD4118A3D0003470C18F00950F3D8@G9JJT.mgb01.telekom.de \
--to=beckw@t-systems.com \
--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;
as well as URLs for NNTP newsgroup(s).