G. Baumgartner and V. F. Russo. " Signatures: A C++ Extension for Type Abstraction and Subtype Polymorphism". Technical Report CSD-TR93 -059, Purdue University, September 1993. Home/Search Document Details and Download
Summary Related Articles Check |
This paper is cited in the following contexts:
A Semantics of the Separation of Interface and.. - Eun-Sun Cho Sang-Yong (1996) (Correct)
.... one for subtyping and the other for reuse. From now on, we ll call the separation of interface and implementation, SII , in abbreviation. However each existing mechanism for SII is accompanied by its own semantics of the type system, and there are a lot of different approaches to processing SII[2, 3, 8, 10, 11, 12, 13, 14]. In some languages[2, 10, 12, 13] an interface is allowed to be bound to more than one implementation, while only one implementation is allowed in some languages. In some language definitions, there is no concept of the hierarchy of either types or implementations[13, 14] Some languages ....
....now on, we ll call the separation of interface and implementation, SII , in abbreviation. However each existing mechanism for SII is accompanied by its own semantics of the type system, and there are a lot of different approaches to processing SII[2, 3, 8, 10, 11, 12, 13, 14] In some languages[2, 10, 12, 13], an interface is allowed to be bound to more than one implementation, while only one implementation is allowed in some languages. In some language definitions, there is no concept of the hierarchy of either types or implementations[13, 14] Some languages provides users with the features for ....
[Article contains additional citation context not shown here]
G. Baumgartner and V. F. Russo. " Signatures: A C++ Extension for Type Abstraction and Subtype Polymorphism". Technical Report CSD-TR93 -059, Purdue University, September 1993.
A New Data Abstraction Layer Required For OODBMS - Cho, Han, Kim (1997) (Correct)
....that it can be, for example, a subclass of Deposit itself for code reuse. In current OODBMSs, this situation can be realized by multiple inheritance, as shown in figure 1. However, such multiple inheritance from the mixture of the two independent hierarchies is known to cause serious complexity[4, 8]. And it may be more serious in database applications, because the schema evolution cost, in proportion to the complexity of the schema, is much higher than in conventional object oriented programs. Note that the hierarchy for persistent classes becomes more complicated than originally intended ....
....for a schema class is collected by traversing all the implementations which implement the interface, as well as its sub interfaces in the interface hierarchy tree. 5 Discussions 5. 1 More on class separation Separation semantics of interface and implementations is not new in programming languages[2, 4, 5, 9]. However, not all of them are satisfactory for the classimplementation layer. In this section, we investigate on the separation model appropriate for OODBMSs. First, since database schema designers use subclassing for real world modeling, explicit sub classing specified by users is preferable to ....
[Article contains additional citation context not shown here]
G. Baumgartner and V. F. Russo. " Signatures: A C++ Extension for Type Abstraction and Subtype Polymorphism". Technical Report CSD-TR93 -059, Purdue University, September 1993.
PSL: Protocols and Pragmatics for Open Systems - Lea, Marlowe (1995) (4 citations) (Correct)
....Interface declarations provide a basis for specifying capabilities in open systems at varying levels of precision and formality. An interface describes only those services that other components may depend on, in terms of a set of constraints (e.g. a collection of required operation signatures [9]) on a family of components, not necessarily a complete or closed (nonextensible) description of any given component. Any implementation(s) that provide required functionality may be used. Subtyping regimes over interfaces allow one interface to be described as an extension, refinement, or ....
Baumgartner, G., & V. Russo, "Signatures: A C++ Extension for Type Abstraction and Subtype Polymorphism ", Software---Practice and Experience, 1994.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC