1. 10

  2. 2

    I think I haven’t heard a single piece of Eiffel news in over 15 years. Cool to see that the language is still being actively developed!

    1. 3

      I bring it up fairly often when talking software assurance. It was first, major implementation of Dijkstra’s methods within a programming language that were accessible to and widely deployed in industrial companies. That method, Design-by-Contract, was invented in the mid-1980’s. About a year later, either inspired by or independent of, experiments to do same in Pascal plus experiments in verifying 80’s Ada led to SPARK: DbC-like annotations with automated, theorem for safest, system code you can get without manual methods. Ada 2012 added it afterward albeit not with theorem proving. The SCOOP model for safer, usable, and object-oriented concurrency was also innovative. ETH’s R&D also made it one of the most studied & improved on concurrency models out there with people even formally verifying properties. Got ported to Java by one team. Quite a neat language even though I don’t intend to use it.




    2. 2

      Two Eiffel stories.

      1) One of my profs knew/knows Bertrand Meyer well. Told me about the process of improving the Eiffel language:

      a) Bertrand Meyer fucks up a language feature

      b) Bertrand Meyer argues about said language feature with people both online and in meatspace

      c) Time passes

      d) Bertrand Meyer quietly takes those peoples' advice and changes Eiffel

      2) Mid 90s, campus library, study group (campus libraries were a primary source of information even as late as the mid 90s; not so much now). Someone brought this youngish (younger than most in the group) girl, who turned out to be Bertrand Meyer’s daughter. She stridently claimed that Eiffel would overtake other languages in both systems and application programming, and that UNIX and C didn’t have much to do with running the internet.