From: Eray Ozkural <erayo@cs.bilkent.edu.tr>
To: "Alessandro Baretta" <alex@baretta.com>,
"Johan Baltié" <johan.baltie@wanadoo.fr>,
Ocaml <caml-list@inria.fr>,
"Daniel de Rauglaudre" <daniel.de_rauglaudre@inria.fr>
Subject: Re: [Caml-list] Recovering masked methods (with CamlP4?)
Date: Mon, 11 Nov 2002 11:20:09 +0200 [thread overview]
Message-ID: <200211111120.10044.erayo@cs.bilkent.edu.tr> (raw)
In-Reply-To: <3D33FE98.6000001@baretta.com>
Hi Alessandro,
On Tuesday 16 July 2002 14:08, Alessandro Baretta wrote:
>
> I strongly disagree. Inheritance, as pointed out previously
> by someone on this list (I can't remember whom), is a
> syntactic property of classes, whereas subtyping is a
> semantic property of instances. Just now I have received a
> post by John Prevost clarifying this.
>
Precisely. Languages that the "software engineering" culture have spawned
adopt a less-than-rational view of the matter. They have not been able to
distinguish typing from inheritance. The most famous of those languages is
C++. Although C++ tries to make a difference between "private" and "public"
inheritance, it's still a disasterous object system.
I think this distinction becomes much clearer in a theoretical analysis of
class based languages. When we compare the prominent object oriented
languages, it is much easier to see that the approach of ocaml is the logical
generalization of object systems found in imperative languages.
That is also how ocaml puts orthogonality back in the equation.
Still, I observe some well-known flaws in the whole of ocaml object system;
but those are hard to overcome in a graceful extension of core caml such as
ocaml.
Regards,
--
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://mp3.com/ariza
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-11-12 19:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 23:13 [Caml-list] Recovering masked methods Alessandro Baretta
2002-07-16 1:15 ` Jacques Garrigue
2002-07-16 9:28 ` Alessandro Baretta
2002-07-16 9:48 ` Laurent Vibert
2002-07-16 10:08 ` Johan Baltié
2002-07-16 10:10 ` Alessandro Baretta
2002-07-16 9:59 ` Johan Baltié
2002-07-16 11:08 ` [Caml-list] Recovering masked methods (with CamlP4?) Alessandro Baretta
2002-07-16 11:32 ` Johan Baltié
2002-07-16 12:52 ` Alessandro Baretta
2002-07-16 12:26 ` Daniel de Rauglaudre
2002-07-16 12:54 ` Alessandro Baretta
2002-07-17 9:26 ` Daniel de Rauglaudre
2002-07-16 13:32 ` John Prevost
2002-07-16 13:35 ` John Prevost
2002-07-16 14:06 ` Alessandro Baretta
2002-07-16 14:15 ` Johan Baltié
2002-07-16 14:29 ` Alessandro Baretta
2002-11-11 9:20 ` Eray Ozkural [this message]
2002-07-16 10:45 ` [Caml-list] Recovering masked methods John Prevost
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=200211111120.10044.erayo@cs.bilkent.edu.tr \
--to=erayo@cs.bilkent.edu.tr \
--cc=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@inria.fr \
--cc=johan.baltie@wanadoo.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