Meyer, B. Genericity versus inheritance. In OOPLSA '86: Conference proceedings on Objectoriented programming systems, languages and applications (New York, NY, USA, 1986), ACM Press, pp. 391--405.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....are: 1. use an object oriented extension of an existing programming language (such as C [Stroustrup 1986] Objective C [Cox 1986] Lisp flavors [Moon 1986] 2. use an object oriented language that is translated into the target programming language (such as Ei#el, which is translated into C [Meyer 1986]) 3. use an object oriented language augmented with a package for interfacing to other languages within the programming environment (e.g. calling Fortran libraries from C , or whatever) The other fundamental issue is that of run time support for the object environment. This may entail support ....

B. Meyer, "Genericity versus Inheritance", ACM SIGPLAN Notices Proceedings OOPSLA '86, vol. 21, no. 11, pp. 391-405, Nov 1986.

.... language How can we exploit encapsulation to support heterogeneous objects, that is, environments in which di#erent objects may be implemented in various languages with, say, a common object oriented interface language Various answers to these problems have been proposed, and even implemented [Meyer 1986; Nierstrasz 1987a; Scha#ert et al. 1986] We are a long way, however, from having standard solutions, because the object models supported by di#erent languages emphasize di#erent properties of objects. For example, another important discovery is the similarity between Smalltalk style objects ....

B. Meyer, "Genericity versus Inheritance", ACM SIGPLAN Notices Proceedings OOPSLA '86, vol. 21, no. 11, pp. 391-405, Nov 1986.

....object oriented extension to Common Lisp, from Hewlett Packard Labs. Snyd86a] ConcurrentSmalltalk: A concurrent extension to Smalltalk from Keio University, Japan. Yoko86] Ei#el: Statically typed programming language with multiple inheritance and genericity (a la Ada) U Cal, Santa Barbara. [Meye86] Encore: An object management system from Brown University. Zdon85] Emerald: An object based language for distributed applications, with data abstraction and strong typing. University of Washington. Blac86] In Objects and Things, ed. D.C. Tsichritzis, Centre Universitaire ....

B. Meyer, "Genericity versus Inheritance", ACM SIGPLAN Notices, vol. 21, no. 11, pp. 391-405, Nov 1986.

.... Type attributes are closely related to generic classes, in that the example above is equivalent to the following one using genericity: class GC[t # T] feature abstract over the type attribute (with bound) class C inherit GC[T] end bind the parameter to the default value Meyer s [Mey86] comparison of inheritance (with declaration by association) and genericity should be re examined in this light. The careful reader will observe that the special association type like Current can not be explained by type attributes. like Current represents a truly novel aspect of Ei#el of both ....

Bertrand Meyer. Genericity versus inheritance. In Proc. of ACM Conf. on Object-Oriented Programming, Systems, Languages and Applications, pages 391--405, 1986.

....have been supported by means of software generation, since existing object oriented languages typically support only very weak or restricted forms of genericity. This leads us to conclude that, contrary to some early opinions concerning the relative expressive power of genericity and inheritance [35], the notion of genericity is still underestimated as a simple mechanism for providing variability in the way objects are implemented and the way they cooperate, that works well when the possible purposes of a certain software component (e.g. a synchronization mechanism) can be known ahead, as is ....

Bertrand Meyer, "Genericity versus Inheritance," Proceedings OOPSLA '86, ACM SIGPLAN Notices, vol. 21, no. 11, Nov 1986, pp. 391-405.

.... 56 59 The problems of inheritance, subtyping, and recursion are exposed in [33, 14, 15, 5] The separation of subtyping and inheritance is made clear in [32] Slide 58 Emerald is described in [6, 50, 7, 87] Trellis Owl in [95] Slide 60 62 Definitions of class based inheritance are given in [57, 49, 110, 46, 63, 96, 9, 93]. Annotated Bibliography 103 Slide 63 66 The soundness of covariance in Eiffel is questioned in [34] the soundness of the pure Simula version is argued in [60] Slide 67 Typed Smalltalk is developed in [51, 45, 44] A system which preserve recursive structure is described in [78, 77, 83] ....

.... languages are presented in [13, 11] Slide 86 Type inference for simple subtyping is developed in [69, 102, 59, 74, 105, 55, 104] Slide 88 94 Class inference is developed in [101, 45, 79, 76, 4] Slide 96 ML modules are described in [67, 106] Slide 97 Approaches to genericity are discussed in [63, 49, 61, 73, 83]. Annotated Bibliography 104 Slide 98 Multi methods are presented in [53, 72, 24, 25] Slide 99 The Self language is described in [108, 26, 27, 28, 48, 3] ....

Bertrand Meyer. Genericity versus inheritance. In Proc. OOPSLA '86, Object-Oriented Programming Systems, Languages and Applications, pages 391--405. Sigplan Notices, 21(11), November 1986.

....on Lisp. In [7] it has been advocated as the ibuilding blockj for inheritance, and has recently received some attention, see for instance [3, 5, 22] Roughly speaking, a mixin is a class denition parameterized over its superclass (there is some similarity with the parameterized classes of Eiffel [33] and the ivirtual classesj of Beta [31] Let us introduce some informal terminology: ffl an object is the xpoint (fix Gen) of a generator (cf. 13] ffl a generator is a function of a iselfj parameter, returning a record of elds and methods. Then a typical generator value is thus sh Delta ....

B. Meyer, Genericity versus inheritance, OOPSLA'86, ACM SIGPLAN Notices Vol. 21 No. 11 (1986) 391-405.

....and implementation by a reverse mapping, rep, from the abstract type to the concrete one, thereby preventing the possibility of having more than one implementation for a given interface. There are several works which touch the relationship between parametric polymorphism and subtyping. Meyer [15] argues that subtyping is not subsumed by parametric polymorphism (which he calls genericity) His counter example involves assignment statements and is similar in spirit to the problem from which we started how to construct data structures of components whose precise type is not known. We ....

Meyer B., Genericity versus Inheritance. In Proc. ACM Conf. on Object-Oriented Programming: Systems, Languages and Applications, pages 391-405, 1986. 15

....of existing abstract data types, and some sort of message passing to invoke operations on objects of unknown implementation. Several object oriented languages have been designed and implemented, including Smalltalk 80 [GR83] C [Str86, ES90] Trellis Owl [SCW85, SCB 86] Eiffel [Mey86, Mey88, Mey92], Modula3 [Nel91, Har92] CLOS [BDG 88] and T [RA82, Sla87, RAM90] Unfortunately, traditional implementations of object oriented language features, particularly message passing, have been much slower than traditional implementations of their non object oriented counterparts, and this gap in ....

....whether an object is guaranteed to remain local to the current node. The Emerald compiler performs no inlining of user defined methods, however, even when statically bound. 27 3.2. 5 Eiffel Eiffel is a statically typed class based object oriented language supporting multiple inheritance [Mey86, Mey88, Mey92]. Like C and Trellis Owl, Eiffel equates classes with types, and treats subclassing as subtyping. However, Eiffel does not verify that subclasses are legal subtypes of their superclasses, and in fact provides many commonlyused features that violate the standard subtype compatibility rules ....

Bertrand Meyer. Genericity versus Inheritance. In OOPSLA '86 Conference Proceedings, pp. 391-405, Portland, OR, September, 1986. Published as SIGPLAN Notices 21(11), November, 1986.

....proposals did, we won t provide co variance for arrays, since we believe that the complication needed for the related implementation is not worth the advantages one obtains. However we think that the problem of the application of co variant and contra variant subtyping to parametric types (see [Mey86] and [Coo89] deserves further study. 13 Which in Java is the java.lang.ArrayIndexOutOfBoundException 22 class ArrayClient public static void main(String[ s) Cell String [ ac=new Cell String [1] ac[1] new Cell String ( 1 ) String s=ac[1] get( String[ s=new String[0] Cell String[ ....

Bertrand Meyer, Genericity versus inheritance, Conference on Object-Oriented Programming, Systems, Languages and Applications, 1986.

....In object oriented terms this corresponds to the external attributes of a class including all the attributes of its superclasses. This is also known as inclusion polymorphism. Genericity and subtyping are very different in principle and each have there own place in an object oriented framework [82]. Most abstract data type languages (including ACT ONE) incorporate a facility for defining parameterised types. Parameterised types can be statically instantiated at specification time and as such they give rise to a distinct group of behaviours (which just happen to have a similar structure) ....

B. Meyer. Genericity versus inheritance. In Object Oriented Programming Languages Systems and Applications (OOPSLA 86) As ACM SIGPLAN 21, November 1986. BIBLIOGRAPHY 258

....and highlights the advantages of each over the other in terms of expressiveness. Some observations of this section have been previously put forth in [BOW98] which also contains a comparison of virtual types and parameterized classes. 2. 1 Parameterized Classes In his often quoted paper [Mey86] Bertrand Meyer presents parameterized classes as a programming language mechanism in Ei el which combines the bene ts of polymorphism, as in ML, and those of inheritance. Several other programming languages, including CLU [LSAS77] C [ES90] and Sather [Omo93] implement similar features. Most ....

Bertrand Meyer. Genericity versus inheritance. In Object Oriented Programming: Systems, Languages and Applications (OOPSLA), pages 391{ 405, 1986.

.... keyType, entityType, compare ] btn root; public: binaryTree( entityType search( keyType ) void insert( keyType, entityType ) ############################################################################################## Figure 7: A Generic Binary Tree Class [Scha85] and Eiffel [Meye86]. Another language that supports generics of this sort is the most recent version of C , i.e. C v.3.0 [Elli90] A generic class or function in C v.3.0 is called a template. Unlike an E generator class, a template class cannot specify constraints on the instantiating type. However, the member ....

Meyer, B., "Genericity Versus Inheritance," Proc. ACM Conf. on Object-Oriented Programming Systems, Languages and Applications, Portland, Oregon, Sept. 1986.

....semantic models may also facilitate a better understanding of the problem domain being considered and of the strengths and weaknesses of each of the languages. Re use An important aspect of all modelling is the ability to re use previous work. This re use may come in many different forms [13,16,14,11,24]. Translation between languages facilitates the transfer of all types of re use from one domain to the other. 1.4. Translation: SDL to TLA It is difficult to rigorously relate or transform SDL models. Furthermore, SDL, unlike TLA is not well suited to the verification of rigorously ....

B. Meyer. Genericity versus inheritance. In Object Oriented Programming Languages Systems and Applications (OOPSLA 86) As ACM SIGPLAN 21, November 1986.

....: 32 5.2 Variable name prefixes. 33 ix Chapter 1 Introduction In the past two decades advances in hardware and software technology have lead to increasingly larger and more complex software systems [BGM89, Mey88, Mic88, Cox87] In particular, software systems have grown in complexity so much so that software design and maintenance has become a daunting task [Gut77] This increase in complexity has lead to ever increasing software development and maintenance costs. Another reason for the great increase in ....

B. Meyer. Genericity versus inheritance. Journal of Pascal, Ada, & Modula-2, 7(2):13--30, March/April 1988.

.... the fact that the design is reusable does not mean the the code that results from it will be reusable. As Meyer has said: any acceptable solution must in the end be expressible in terms of programs, and programming languages fundamentally shape the software designers way of thinking [9]. This means that whatever programming language is used must have features that allow the creation of reusable code, and those features must be properly used. We believe that object oriented programming languages do provide appropriate features for creating reusable code, but that the correct use ....

Bertrand Meyer. Genericity versus inheritance. In Norman Meyrowitz, editor, 1986 Object-Oriented Programming Systems, Languages, and Applications Conference Proceedings, pages 291--405, October 1986. Published as ACM SIGPLAN Notices, 21(11), November 1986.

.... in turn a concrete module (in other words, the dependency between the two modules is only in one direction) A formalization of this point of view could clarify the relation between inheritance and genericity, which has been a topic of great debate in the object oriented community (see, e.g. [12]) Acknowledgements. We would like to thank the anonymous referees for their useful comments and suggestions. ....

B. Meyer. Genericity versus inheritance. In ACM Symp. on Object-Oriented Programming: Systems, Languages and Applications 1986, pages 391--405. ACM Press, November 1986. SIGPLAN Notices, 21, 11.

No context found.

Meyer, Bertrand. "Genericity versus Inheritance". Proc. OOPSLA'86, Sigplan Not. 21,11 (Nov. 1986),391-405.

No context found.

Meyer, B. Genericity versus inheritance. In OOPLSA '86: Conference proceedings on Objectoriented programming systems, languages and applications (New York, NY, USA, 1986), ACM Press, pp. 391--405.

No context found.

B. Meyer. Genericity versus inheritance. In Proceedings of the Conference on Object Oriented Programming Systems Languages and Aplications (OOPSLA), pages 391--405, Portland, OR, USA, 1986.

No context found.

B. Meyer. Genericity versus inheritance. In ACM Symp. on Object-Oriented Programming: Systems, Languages and Applications 1986.

No context found.

Bertrand Meyer. Genericity Versus Inheritance. Journal of Pascal, Ada & Modula2 7(2):13-30, March/April 1988.

No context found.

B. Meyer. Genericity versus inheritance. In Proceedings of the Conference on Object Oriented Programming Systems Languages and Aplications (OOPSLA), pages 391--405, Portland, OR, USA, 1986.

No context found.

Meyer B., Genericity versus Inheritance, Journal of Pascal, Ada & Modula-2, vol. 7, 2 (march-april 1988), pp. 13-30

No context found.

Bertrand Meyer. Genericity versus Inheritance. In OOPSLA '86 Conference Proceedings, pp. 391-405, Portland, OR, September, 1986. Published as SIGPLAN Notices 21(11), November, 1986.

First 50 documents

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