From: Jeff Meister <nanaki@gmail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: david.baelde@ens-lyon.org, Chris Yocum <cyocum@gmail.com>,
caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml and the Fragile Base Class Problem
Date: Sat, 27 Aug 2011 13:21:32 -0700 [thread overview]
Message-ID: <CAHaHOqRCOqWzyPcnQpGH=LUNiMkJsSwcExqALZv5yVwuGMU36g@mail.gmail.com> (raw)
In-Reply-To: <1314473840.3496.132.camel@thinkpad>
I don't understand this part. You can easily hide a public method of
an object by coercing it to an object type which does not have that
method. Modules also provide excellent information hiding: if you
don't want anyone else calling your method, make at least one of its
input types abstract in the interface, and don't provide any values of
that type.
On Sat, Aug 27, 2011 at 12:37 PM, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:
> I guess the biggest problem is that structural
> typing does not offer much for getting information hiding - once a
> method is public, it is fully public. This is, in some sense, against
> the mindset of the typical OCaml programmer.
next prev parent reply other threads:[~2011-08-27 20:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 10:53 Chris Yocum
2011-08-27 11:24 ` Jacques Garrigue
2011-08-27 15:06 ` Gerd Stolpmann
2011-08-27 16:59 ` David Baelde
2011-08-27 19:37 ` Gerd Stolpmann
2011-08-27 20:21 ` Jeff Meister [this message]
2011-08-27 23:08 ` Gerd Stolpmann
2011-08-28 9:31 ` Andreas Rossberg
2011-08-28 10:04 ` Guillaume Yziquel
2011-08-28 10:11 ` Gerd Stolpmann
2011-08-28 10:50 ` Andreas Rossberg
2011-08-29 3:35 ` Jacques Garrigue
2011-08-29 11:19 ` Chris Yocum
2011-08-29 11:47 ` Guillaume Yziquel
2011-08-29 12:03 ` Chris Yocum
2011-08-31 21:33 ` Alain Frisch
2011-08-31 23:39 ` Jacques Garrigue
2011-08-28 17:58 ` Julien Signoles
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='CAHaHOqRCOqWzyPcnQpGH=LUNiMkJsSwcExqALZv5yVwuGMU36g@mail.gmail.com' \
--to=nanaki@gmail.com \
--cc=caml-list@inria.fr \
--cc=cyocum@gmail.com \
--cc=david.baelde@ens-lyon.org \
--cc=info@gerd-stolpmann.de \
/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).