Eiffel
by Bertrand Meyer · first published 1991
7mentions
0recommended by
7HN commenters
2015–2025first – last mentioned
100% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
by Bertrand Meyer · first published 1991
100% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
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…
on “Green vs. Brown Programming Languages” ↗…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…
on “Professional Software Development” ↗> 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…
on “Eiffel programming language” ↗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,…
on “Dependency Injection, Inversion of Control and the Dependency Inversion Principle” ↗…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…
on “Object-oriented Programming with ANSI-C (1993) [pdf]” ↗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…
on “Mostly dead influential programming languages (2020)” ↗…(I borrow this list from Bertrand Meyer's OOSC, 2nd edition), language compilers tend to shift the burden from the compiler to the programmer to manage types etc. It is probably too late to go back to Eiffel, though, I still think that it even today is far ahead of most oo languages, so if folks feel strongly against oo, I can understand that to some extent. I recall a small exercise,where I was modeling…
on “The Humble Programmer” ↗