From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Type notation in OO-layer
Date: Fri, 3 Aug 2007 23:29:00 +0200 [thread overview]
Message-ID: <1186176540.46b39e1c6f460@webmail.in-berlin.de> (raw)
In-Reply-To: <1186175921.46b39bb1508b1@webmail.in-berlin.de>
Zitat von Oliver Bandel <oliver@first.in-berlin.de>:
[...]
> As it is not a true "unit"-function, we at least should give it a
> unit-like type like "message -> string" so that the type-system
> make a complete annotation of type?!
OK, I had misleading thoughts here: not the method get's the message,
the object gets the message.
So, the type of the function is OK.
But shouldn't the message be somewhere else notated?
Or is this thrown out in general, when using OO?
I sthere no contradiction, when using such a type annotation,
when comparing it to the non-OO stuff?
TIA,
Oliver
next prev parent reply other threads:[~2007-08-03 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 21:18 Oliver Bandel
2007-08-03 21:29 ` Oliver Bandel [this message]
2007-08-04 0:38 ` [Caml-list] " Jacques GARRIGUE
2007-08-04 3:28 ` Julien Moutinho
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=1186176540.46b39e1c6f460@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--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).