| William Cook. A proposal for making Ei#el type-safe. In Proc. of the 3rd ECOOP, pages 57--70, Nottingham, England, July 1989. Cambridge University Press. |
....the air in the late 1980s. The first edition of Meyer s book on OO software construction in Ei#el [Mey88] gives one of the first accounts of the idea. Unfortunately, Ei#el has an unsound definition of behavioral subtyping, because the language s type system has an unsound definition of subtyping [Coo89] America gave the first sound definition of behavioral subtyping that appeared in print [Ame87] reworked in [Ame91] he emphasized the need for contravariance and gave a simple proof of the soundness of his rule based on Hoare s rule of consequence. The simple version of America s definition ....
Cook, W. R. A proposal for making ei#el type-safe. The Computer Journal, 32(4):305--311, August 1989.
....Ei el rejected the restrictions imposed by Trellis Owl and allowed the use of like Current as the type of parameters of methods and as the type of instance variables. Unfortunately, the free use of this construct and the identi cation of subclasses with subtypes leads to type insecurities [Coo89] We illustrate this problem with an example. As will be clear when we give the formal de nition of matching, in our example above, DNodeType # NodeType, but we claim it is not a subtype. Suppose we write the following PolyTOIL procedure: breakIt = procedure(sn1, sn2: NodeType) ....
William R. Cook. A proposal for making Eiel type-safe. In European Conf. on Object-Oriented Programming, pages 57-72, 1989.
No context found.
William Cook. A proposal for making Ei#el type-safe. In Proc. of the 3rd ECOOP, pages 57--70, Nottingham, England, July 1989. Cambridge University Press.
No context found.
W. Cook. A Proposal for Making Ei#el Type-safe. In ECOOP 1989.
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