We are please to announce the release of our new Eiffel Support Site , designed with a fresh new look and user friendly navigation enabling you to access it from different devices and backed up by a new API using Hypermedia  , concept
An Eiffel program is a complex data structure. It is made out of attributes, local variables, types, classes, instructions, feature calls, assignment attempts and a lot more. These constructs reference each other: attributes are used by features, features contain instructions, instructions use local variables, local variables reference types, types are built from classes, and so forth.
When we look at the textual representation (the code text) of an Eiffel program, we identify two major ways that these relations are expressed.
The past 6 months we have been working on some new language improvements to simplify and improve the expressiveness of Eiffel.
The first improvement is the conditional expression. Very often, depending on some boolean value you expect either one result or another. Although one can express this, it is sometime tedious and/or not very readable.
Coming up on December 3rd and 4th in Zurich, Switzerland, we will be hosting the second Eiffel Design Feast solely focused on the Web solution(s) for Eiffel. The first event back in June was a real success and we hope to achieve the same kind of results.
This time around we will be checking the results of the work since last time.
In Eiffel (to the best of my knowledge), a class B that inherits from a parent class A has access to all features of A. So far this hasn't bothered me at all, to the point that I often change my private functions in C# to protected.
But recently, as I was writing Eiffel programs to practice SCOOP, it occurred to me that I must now write a lot more features than I would before.