From: Pierre CASTERAN <Pierre.Casteran@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Weak types ?
Date: Tue, 3 Feb 1998 16:46:22 +0100 (MET) [thread overview]
Message-ID: <199802031546.QAA21882@scrasmeustache.labri.u-bordeaux.fr> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]
Hello, all.
I suppose the following problem concerns "weak" types, but i don't see
the reason (I have no assignment at all in this definitions !)
let toto =
let id x = x
in id id;;
(*
val toto : '_a -> '_a = <fun>
^ ^
why not " 'a " ?
*)
toto 5;;
(* ok *)
toto (fun z -> z);;
(*
This expression has type 'a -> 'a but is here used with type int
*)
If i remember Xavier's works, the "weak" types were necessary for
dealing with references, continuations/exceptions, and i/o streams,....
What's the problem with these gentle purely functional top-level
definitions ?
Pre Scriptum :
I (still ) work with Objective Caml version 1.03
--
Pierre Casteran,
LaBRI, Universite Bordeaux-I | 12 place Puy Paulin
351 Cours de la Liberation | 33000 Bordeaux
F-33405 TALENCE Cedex | France
France | (+ 33) 5 56 81 15 80
tel : (+ 33) 5 56 84 69 31
fax : (+ 33) 5 56 84 66 69
email: Pierre . Casteran @ labri . u-bordeaux . fr (but whithout white space)
www: http://dept-info.labri.u-bordeaux.fr/~casteran
"Combien de petites violences la verité et l'analyse subissent-elles
quotidiennement dans le silence de nos pensées engourdies ?"
[Serge Halimi, in "Les nouveaux chiens de garde" (Liber, ed.)]
next reply other threads:[~1998-02-04 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-03 15:46 Pierre CASTERAN [this message]
1998-02-04 19:07 ` Simon Helsen
1998-02-05 16:05 ` Juan J. Quintela
1998-02-09 16:00 ` Pierre Weis
1998-02-09 16:31 ` Simon Helsen
1998-02-10 18:51 ` Pierre Weis
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=199802031546.QAA21882@scrasmeustache.labri.u-bordeaux.fr \
--to=pierre.casteran@labri.u-bordeaux.fr \
--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