5 ms·
I looked at Eiffel seriously in the late nineties. My issue was interoperability and libraries. A little later, he tried Eiffel.NET, but I had moved on by then
by loumf 13y ago
I looked at Eiffel seriously in the late nineties. My issue was interoperability and libraries. A little later, he tried Eiffel.NET, but I had moved on by then.
Eiffel's main selling points (safer, purer OO) were eventually credibly implemented in Java and C#, and people who wanted something else, wanted something really different.
Not sure anyone really wanted Eiffel's extensive (and sane) multiple inheritance support. I certainly wanted pre/post conditions and thread-safety.
- pjmlp 13y agoWhat attracted me to Eiffel, in the mid nineties, was the whole concept of design by contract, better OO than C++, compilation to native code, GC and belonging to the Pascal family of languages. What putted me off was Eiffel Studio's price as university student, without knowing if the language would have any industry influence.
- phpnode 13y agoEiffel's contracts are really compelling, I wish there was a reasonable, non-hacky way to implement them in more mainstream languages.
- loumf 13y agoI wouldn't say that clojure is mainstream, but their implementation is reasonable and makes sense in the clojure idiom (just a meta-data map on the function)
- phpnode 13y agoTurns out there's a sort of reasonable way to implement them in JavaScript, it's definitely hacky though - http://codemix.github.io/contractual/try.html http://codemix.github.io/contractual/try.html
- squidsoup 13y agoClojure provides a nice equivalent of pre/post conditions in core.contracts, check it out perhaps.