B. Meyer. Interactive software engineering. http://ei#el.com/, 2001. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Fully Object-Oriented Exception Handling System: - Rationale And Smalltalk (2001) (Correct)
.... have all been influenced by Goodenough s seminal paper [7] Well known implementations include MESA [15] CLU [13] or ADA [8] Exception handling systems have later been integrated into object oriented languages at the end of the 1980s (Zetalisp Flavors [17] CommonLisp( CLOS) 19] Eiffel [14], Objectworks Smalltalk [21] C [11] or more recently in Java. This papers presents an overview of the specification and implementation of an exception handling system initially conceived [3] for the Lore Object Oriented Language and adapted to Smalltalk [4] The key ideas of this system are ....
B.Meyer: Disciplined exceptions. Interactive Software Engineering, TR-EI-22/EX, 1988.
The Complexity of Type Analysis of Object Oriented Programs - Gil, Itai (1998) (6 citations) (Correct)
....that OOTA has also applications to type checking in co variant languages such as EIFFEL [M92] In order to type check the arguments to a method call, it is necessary to determine the set of classes the receiver might assume. This is done for example in Meyer s polymorphic catcalls algorithm [M95]. 1.2 Results Before stating our results, a brief overview of complexity classes may be in place. For more information, the reader may consult a textbook, such as Hopcroft and Ullman [HU79] or David Johnson s survey paper [J90] The most familiar complexity class is NP the class of all sets ....
Meyer B., Beware of Polymorphic Catcalls, White paper, Interactive Software Engineering, 1995. In http://www.eiffel.com/doc/manuals/technology/typing/cat.html
Parents are Shared Parts of Objects: Inheritance and.. - Chambers, Ungar.. (1991) (18 citations) (Correct)
....has two drawbacks: it masks ambiguities between otherwise unordered ancestors, and it fails with inheritance graphs that it deems inconsistent. The opposite approach to resolving ambiguities among an object s parents is to leave it up to the programmer. Languages like Trellis Owl [17, 18] Eiffel [14, 15], C version 2.0 [23, 24] and CommonObjects [20, 21] treat an object s parents as equals without a relative ordering and treat ambiguities as programming errors that need to be explicitly resolved by the programmer. 3 We call this approach unordered inheritance. It works best when combining ....
Meyer, B. Eiffel: An Introduction, Version 2.1. TR-EI-3/GI, Interactive Software Engineering, Inc., Goleta, CA (1988).
Attaching Second-Order Types to Methods in an Object-Oriented .. - Caseau, Perron (1993) (1 citation) (Correct)
.... We suppose two important hypotheses : supports inclusion polymorphism (e.g. integer number) is extensible (new classes c can be added with a method c) A correctly typed definition of the min feature has already been given when one of the hypotheses holds (e.g. ABC[GMP90] Eiffel[Me89]) If we consider the following method definition, which represents the min feature (entity is the set of everything) Example: 1 [define min(x:entity, y:entity) method object = if (x y) x else y] This method will not yield static type checking, since it is defined on the class object ....
B. Meyer : Static Typing for Eiffel. Interactive Software Engineering, July, 1989.
Is MDA achievable without a proper definition of late-binding? - Beugnard (2002) (Correct)
No context found.
B. Meyer. Interactive software engineering. http://ei#el.com/, 2001.
Strategic Research Directions in Object Oriented Programming - Guerraoui (1996) (5 citations) (Correct)
No context found.
B. Meyer. Eiffel: The Language, version 2.2. Interactive Software Engineering, Inc., Santa Barbara, CA, USA, 1989.
Strategic Research Directions in Object Oriented Programming - Rachid Guerraoui (1996) (5 citations) (Correct)
No context found.
B. Meyer. Eiffel: The Language, version 2.2. Interactive Software Engineering, Inc., Santa Barbara, CA, USA, 1989.
A Concurrency Mechanism For Sequential Eiffel - Karaorman, Bruno (1992) (3 citations) (Correct)
No context found.
Meyer, B., Eiffel : The Libraries. Version 2.2, TR-EI-7/RM, Interactive Software Engineering, Goleta CA, August 1989.
A Concurrency Mechanism For Sequential Eiffel - Karaorman, Bruno (1992) (3 citations) (Correct)
No context found.
Meyer, B., Eiffel : The Language. Version 2.2, TR-EI-17/RM, Interactive Software Engineering, Goleta CA, December 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