From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p7SA6bMv023387 for ; Sun, 28 Aug 2011 12:06:37 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoAAGQSWk5V2gB4mWdsb2JhbABCqAsBAQEBAQgLCwcUJYFAAQEFeRALGC4UKCGIB7YfDoY+BKQl X-IronPort-AV: E=Sophos;i="4.68,292,1312149600"; d="scan'208";a="117434592" Received: from emailfrontal1.citycable.ch ([85.218.0.120]) by mail1-smtp-roc.national.inria.fr with SMTP; 28 Aug 2011 12:06:33 +0200 X-Alinto-smtpauth-localdomain: Yes Received: from seldon (unknown [85.218.93.239]) (Authenticated sender: guillaume.yziquel@citycable.ch) by emailfrontal1.citycable.ch (Postfix) with ESMTPA id A9030E64114; Sun, 28 Aug 2011 12:06:26 +0200 (CEST) Received: from yziquel by seldon with local (Exim 4.72) (envelope-from ) id 1QxcEQ-0008EP-Ae; Sun, 28 Aug 2011 12:04:46 +0200 Date: Sun, 28 Aug 2011 12:04:46 +0200 From: Guillaume Yziquel To: Andreas Rossberg Cc: Gerd Stolpmann , Jeff Meister , david.baelde@ens-lyon.org, Chris Yocum , caml-list List Message-ID: <20110828100446.GS4564@localhost> References: <4E58CCC3.4040901@gmail.com> <1314457588.3496.86.camel@thinkpad> <1314473840.3496.132.camel@thinkpad> <1314486489.3496.179.camel@thinkpad> <00776888-5A29-4575-BAAC-A27B3F2A8FE3@mpi-sws.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <00776888-5A29-4575-BAAC-A27B3F2A8FE3@mpi-sws.org> User-Agent: Mutt/1.5.20 (2009-06-14) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id p7SA6bMv023387 Subject: Re: [Caml-list] Ocaml and the Fragile Base Class Problem Le Sunday 28 Aug 2011 à 11:31:35 (+0200), Andreas Rossberg a écrit : > On Aug 28, 2011, at 01.08 h, Gerd Stolpmann wrote: > > > >Let me point out one final thing. Information hiding is simply not a > >core concept of OO - which is in the first place a specific way of > >structuring the program (e.g. group data and algorithms together), > >with > >an integrated method of adapting object types (subtyping), and giving > >control of parts of your algorithm to the user of your class. > > Not sure why you would say that. Information hiding and extensibility via C++ virtual member functions are orthogonal concepts. It seems to me that, historically, the benefit of OO was essentially code organisation and reusability. Making it "easier" was the main benefit over C. Compared to that, information hiding isn't that great of a benefit compared to what you could already do in C. In a sense, information hiding is more of a refinement, and not the core concept of OO. At least that my take on it. -- Guillaume Yziquel