https://www.amazon.com/Eiffel-Language-PRENTICE-HALL-OBJECT-... > Quickly emerging as the language of choice for developers of quality software, this guide explains how the Eiffel language combines rigorous software engineering principles…
…Guarantees no interface errors, which are 80+% of software faults. Today's tools have better notations & performance but still can't do all that for general-purpose systems: always a niche. https://www.eiffel.com/values/design-by-contract/introductio... Note: Added Eiffel method to make up for fact that I have little to nothing on OOP given I don't use OOP. Meyer et al get credit for a powerful combo of language…
> I don’t think Meyer understood that the era of free compilers had begun. It arguably hadn't. OOSC came out in '88, and that was probably the first big push of Eiffel. The dedicated book and the release of their IDE "EiffelBench" followed in '90. Free compilers weren't an issue for either commercial nor desktop customers. But the market for the big OO language was…
http://en.wikipedia.org/wiki/Class_invariant (above is a special case of below) http://en.wikipedia.org/wiki/Design_by_contract Alas, Eiffel looked like Modula (Pascal), rather than like C/C++, so it never caught on. The important part, though, was the idea of class invariants + method pre-conditions + method post-conditions. Meyer's book,…
…thorough, precise and detail-oriented that it can become tedious at times. Take your time going through the book to get the big picture of his OO design/implementation arguments rather than the details of the Eiffel language (not necessary during the first pass). It is a huge book so skip topics as needed to focus on the essential concepts. You should also look into Meyer's "Design By Contract" technique for writing…
What about Eiffel? What are people's thoughts about it? I know a little about its history, and had tried it out a bit, some years ago, via the EiffelStudio trial edition, IIRC. I had also read a good chunk of Bertrand…
https://www.amazon.com/Eiffel-Language-PRENTICE-HALL-OBJECT-... > 迅速成为高质量软件开发者的首选语言，这本指南讲解了 Eiffel 语言如何结合严谨的软件工程原则……
https://www.amazon.com/Eiffel-Language-PRENTICE-HALL-OBJECT-... > Quickly emerging as the language of choice for developers of quality software, this guide explains how the Eiffel language combines rigorous software engineering principles…
……保证没有接口错误，而接口错误占软件故障的 80% 以上。今天的工具记法和性能都更好了，但仍然无法为通用系统做到这一切：始终是个小众领域。https://www.eiffel.com/values/design-by-contract/introductio... 注：补充了 Eiffel 方法，因为我不使用 OOP，所以关于 OOP 几乎没什么可说的。Meyer 等人功在把语言……的强大组合
…Guarantees no interface errors, which are 80+% of software faults. Today's tools have better notations & performance but still can't do all that for general-purpose systems: always a niche. https://www.eiffel.com/values/design-by-contract/introductio... Note: Added Eiffel method to make up for fact that I have little to nothing on OOP given I don't use OOP. Meyer et al get credit for a powerful combo of language…
> 我不认为 Meyer 明白免费编译器的时代已经开始了。可以说当时还没有。OOSC 于 88 年出版，那大概是 Eiffel 的第一次大推进。专门的书和他们的 IDE“EiffelBench”的发布在 90 年紧随其后。免费编译器对商业客户和桌面客户都不是问题。但大型 OO 语言的市场……
> I don’t think Meyer understood that the era of free compilers had begun. It arguably hadn't. OOSC came out in '88, and that was probably the first big push of Eiffel. The dedicated book and the release of their IDE "EiffelBench" followed in '90. Free compilers weren't an issue for either commercial nor desktop customers. But the market for the big OO language was…
http://en.wikipedia.org/wiki/Class_invariant（上面是下面的特例）http://en.wikipedia.org/wiki/Design_by_contract 唉，Eiffel 看起来像 Modula（Pascal），而不像 C/C++，所以一直没流行起来。不过重要的部分是类不变式 + 方法前置条件 + 方法后置条件这个想法。Meyer 的书，……
http://en.wikipedia.org/wiki/Class_invariant (above is a special case of below) http://en.wikipedia.org/wiki/Design_by_contract Alas, Eiffel looked like Modula (Pascal), rather than like C/C++, so it never caught on. The important part, though, was the idea of class invariants + method pre-conditions + method post-conditions. Meyer's book,…
……内容详尽、精确、注重细节，以至于有时会显得冗长乏味。读这本书时要慢慢来，把握他关于面向对象设计与实现论证的整体思路，而不是纠结于 Eiffel 语言的细节（第一遍读时没必要）。这书很厚，可以按需跳过一些主题，专注于核心概念。你还应该研究一下 Meyer 的“契约式设计”技术，用来编写……
…thorough, precise and detail-oriented that it can become tedious at times. Take your time going through the book to get the big picture of his OO design/implementation arguments rather than the details of the Eiffel language (not necessary during the first pass). It is a huge book so skip topics as needed to focus on the essential concepts. You should also look into Meyer's "Design By Contract" technique for writing…
Eiffel 怎么样？大家怎么看它？我对它的历史略知一二，几年前还试用过一下 EiffelStudio 试用版，如果我没记错的话。我也读过不少 Bertrand……
What about Eiffel? What are people's thoughts about it? I know a little about its history, and had tried it out a bit, some years ago, via the EiffelStudio trial edition, IIRC. I had also read a good chunk of Bertrand…