Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Delegation based OO
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2004-03-24 (15:00)
From: Alex Baretta <alex@b...>
Subject: Re: [Caml-list] Delegation based OO
Yamagata Yoriyuki wrote:
>>Delegation is no relative of inheritance. Inheritance is a syntactic 
>>property (essentially classes inherit code), whereas delegation is a 
>>semantic property: once one method is delegated by a proxy object to an 
>>executor object, the the visibility of the proxy is lost. The method is 
>>executed as if it were invoked directly on the executor.
> There is a certain approach (object-based OO) which makes inheritance
> to be a relation between objects (and get rid of the concept of class
> altogether).  In this approach, we can add, and modify mothods in
> objects in run time.  I confuse this with Alex proposal.

"Object based object orientation" is simply horrible English. 
"Delegation based object orientation" is both more expressive of what 
really goes on behind the scenes and more appropriate from a linguistic 

What you have in mind is JavaScript, a delegation based 
object-functional language with dynamic typing. What Jacques and I are 
discussing is a class-and-delegation based object-functional paradigm, 
an extension to ocaml's present class based object-functional approach.


To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: