RE: [opengoop inheritance] Virtual Methods should be called Dynamic Methods

[Dan P. <Dan...@ga...>]

I think abstract is the wrong term.  The OpenG definition of a"Virtual
Method" is "A Virtual Method is one which may be overrided by a descendant
class. It is created from a special Virtual Method template, that has the
ability to look for and dynamically execute descendent class implementations
of the method, or else call its own implementation of the method. "  It is
clearly not an abstract method, at least as the term is used in Java.
Abstract methods do not have implementations.

I don't think it is confusing to use the term Virtual Method, as here it is
used in the same way as in Endevo's GOOP Wizard 3.  If there is a need to
use a different term, and if Dynamic isn't quite right, how about something
along the lines of Overridable Base Method or Dynamically Overridable
Method.

On a slight different topic, I do think there needs to be an Abstract Method
construct.  The way Endevo handled it seems to be an afterthought and has at
least one flaw, according to their white paper.

----- Original Message ----- --__--__--

Message: 2
From: "Jim Kring" <ji...@ji...>
To: <ope...@li...>
Subject: RE: [opengoop inheritance] Virtual Methods should be called Dynamic
Methods
Date: Fri, 7 Nov 2003 00:52:58 -0800
Reply-To: ope...@li...

Niels and Bj=F8rnar,

After listening to the arguments you both make, I agree that "abstract"
might be the best term to use, rather than "dynamic".  Also, I think =
that
"prototype" has an OOP design pattern (Gang of Four) definition and
"template" has an edit-time connotation, which make these two choices =
not
very attractive.

-Jim