From: Dan Grossman <djg@cs.washington.edu>
To: David Teller <David.Teller@ens-lyon.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OO design
Date: Mon, 08 May 2006 14:36:07 -0700 [thread overview]
Message-ID: <445FB9C7.4040703@cs.washington.edu> (raw)
In-Reply-To: <200605082329.36911.David.Teller@ens-lyon.org>
Phantom types are a programming idiom that can often pull off this sort
of thing.
--Dan
David Teller wrote:
> On Monday 08 May 2006 05:17, Jacques Garrigue wrote:
>
>>I would be tempted to say: there is no answer.
>>Ocaml objects are not about enforcing protocols, but about allowing
>>inheritance and structural subtyping, and this does not fit well with
>>your problem.
>
>
> Which brings us to a question : how do you enforce protocols in OCaml ?
>
> Say, is there a "good" way of rewriting file-related operations so that, say,
> ProtocolUnix.read and ProtocolUnix.write *statically* only accept opened
> files, and in addition, ProtocolUnix.write only accepts files which have been
> opened with write priviledges ?
>
> I mean, there are manners of checking this with, say, model checking tools. In
> the specific case of file management, I guess we can do it with a little bit
> of simple subclassing, but I assume there's a large run-time penalty for this
> extra bit of checking, due to the management of objects by OCaml. Has anyone
> attempted to determine how well this scales up ? Or explored other options ?
>
> Cheers,
> David
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2006-05-08 21:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 9:35 David Baelde
2006-05-05 10:47 ` [Caml-list] " Gerd Stolpmann
2006-05-05 13:00 ` Remi Vanicat
2006-05-05 19:32 ` Andrej Bauer
2006-05-08 3:17 ` Jacques Garrigue
2006-05-08 21:29 ` David Teller
2006-05-08 21:36 ` Dan Grossman [this message]
2006-05-10 2:41 ` Geoffrey Alan Washburn
2006-05-10 16:17 ` [Caml-list] " Dan Grossman
2006-05-10 18:15 ` Geoffrey Alan Washburn
2006-05-10 18:44 ` [Caml-list] " Dan Grossman
2006-05-10 18:35 ` Shawn
2006-05-10 18:47 ` Till Varoquaux
2006-05-10 19:01 ` Shawn
2006-05-10 18:43 ` brogoff
2006-05-11 0:08 ` Geoffrey Alan Washburn
2006-05-11 5:45 ` [Caml-list] " Till Varoquaux
2006-05-11 6:21 ` Jacques Garrigue
2006-05-11 15:48 ` Geoffrey Alan Washburn
2006-05-08 22:59 [Caml-list] " yoann padioleau
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=445FB9C7.4040703@cs.washington.edu \
--to=djg@cs.washington.edu \
--cc=David.Teller@ens-lyon.org \
--cc=caml-list@yquem.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).