B. Meyer, `Eiffel---a language and environment for software engineering', The Journal of Systems and Software, 8, (3), 199--246 (1988).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....module normally implements a number of functions. A function with a limitation of the input domain is usually referred to as a partial function [16] and to ensure that only legal values are passed to the function, the precondition of the function must be satisfied. Some languages such as Eiffel [12, 13, 14] have assertion statements to ensure that semantic properties of modules are not violated, but most programming languages leave this task to the programmer. 3 Quality Criteria in Programming There is a number of different metrics of software quality. Many of these metrics heavily rely on ....

Meyer, Bertrand, Eiffel: a Language and Environment for Software Engineering in Journal of Systems and Software, 1988

....it is important to preserve the original syntactic format. For example, in certain deductive steps a free variable in such a term can be renamed or 2 Where possible it is of course desirable that tool elements should also share semantic entities (and hence abstract syntax semantics) 3 Eiffel [9] does allow the argument to a template to be constrained to be a sub class of a given class. 4 In HOL for example, Let x=e in t is denoted by LET( l x.t) e) where LET is a marker constant defined equal to the identity function. 6 instantiated. These substitutions should not coerce distinct ....

Meyer B, Eiffel: a language and environment for Software Engineering, Journal of Systems and Software, vol. 8, pages 199-246, 1988.

....its own concept of type system. Usually, these different type systems are incompatible, in the sense that a correct hierarchy in one language can not be easily translated to another language. Differences arise in points like single versus multiple inheritance (e.g. Beta [KMMPN90] versus Eiffel [Mey88a] separate hierarchies for types and classes (e.g. Pool [AvdL90] and DuoTalk [Lun89] possibility of redefinition of signatures of inherited methods (e.g. C [Str92] does not allow, while Eiffel does) and many other topics. One of the reasons for those differences is the lack of a clear ....

Bertrand Meyer. Eiffel -- a language and environment for software enginnering. The Journal of Systems and Software, 8(3):129--46, 1988.

....of T s specification. In specification terms this means that for each method M specified both in S and T , the pre condition of M in T implies the precondition of M in S and the post condition of M in S implies the post condition of M in T . Formal requirements for such behavioral subtyping [Mey88a, LW90, Ame90, Lea91, LW93a, LW93b] involve either semantic modeling or theorem proving. The Larch proof assistant LP [GH93, Chapter 7] because it accepts LSL syntax, could be used to prove such properties. Larch Smalltalk itself checks only for the traditional syntactic constraints, which we ....

Bertrand Meyer. Eiffel: A language and environment for software engineering. The Journal of Systems and Software, 8(3):199--246, June 1988.

.... differing from others in points like single versus multiple inheritance (e.g. Beta [15] versus CommonLisp [4] separate hierarchies for types and classes (e.g. Pool [2] and DuoTalk [16] possibility of redefinition of signatures of inherited methods (e.g. C [10] does not allow, while Eiffel [17] does) and many other topics. Usually, the formalization of OO type concepts is done by translating these concepts into a more formal language, like typed lambda calculus or an algebraic framework [9] Some advantages of this approach are the use of a simple and well understood framework and ....

....any kind of data. Again we emphasize that our goal is to provide completeness, and not efficiency. Private Methods A private method is a method that is not visible outside the class where it is defined. Many OO languages offer a special mechanism for this facility, e.g. C [10] and Eiffel [17]. School, with its separation between implementations and specifications, presents a natural way to support private methods. Whenever a routine is defined in an implementation but not in its correspondent specification, it is private. However, in order to support this simple idea, we must change a ....

Bertrand Meyer. Eiffel -- a language and environment for software enginnering. The Journal of Systems and Software, 8(3):129--46, 1988.

....the procedural programming and the latter is the next level of abstraction from the object oriented one. Software reuse is, or at least should be, a natural part of both of these paradigms and it has been explored in some forms elsewhere and implemented in such environments as C [Lip91] Eiffel [Mey88] and others [KMMPN87] In this section we will discuss the previous approaches to this problem and outline how our approach differs from them. It has been shown in many studies [IEE84] both empirical and theoretical, that the object oriented paradigm and software reuse are very closely related. ....

B. Meyer. Eiffel: Language and environment for software engineering. The Journal for Systems and Software, 8(3), 1988.

....the boundaries between the layers of abstraction are mostly invisible, with no formal definition. Both customers and system developers have difficulty choosing a level of abstraction for a problem and staying in its boundaries. Eiffel is a language and environment for software development [51]. The language supports static type checking, object oriented programming, exception handling, and systematic use of assertions and invariants. The type system is integrated with the CHAPTER 2. RELATED WORK 16 object system by using the inheritance relation to represent the subtype relation. An ....

Meyer, B. Eiffel: A language and environment for software engineering. The Journal of Systems and Software (1988).

No context found.

B. Meyer, `Eiffel---a language and environment for software engineering', The Journal of Systems and Software, 8, (3), 199--246 (1988).

No context found.

B. Meyer, "Eiffel: A Language and Environment for Software Engineering", Interactive Software Engineering, Inc, 1987

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