blog When parentheses matter

Recently I've run into an issue that can be summarized by the following code snippet:


Question 1. Will   and   have the same value?

blog Some lazy data structures implemented in Eiffel - Part I - Iterating the Calkin-Wilf tree

colin-adams's picture

This is the first part of a series in which I intend to make some explorations of lazy, infinite data structures in Eiffel.

blog A colored year on the web for Eiffel

conaclos's picture

Happy new year!

ACE, Prism, and Rouge now support the syntax highlighting of the Eiffel language.


Prism is by-design a lightweight syntax highlighter for the web. It is very simple to use, and the download page enables to get only what you need.

blog New Eiffel Support Site

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 [1] ,[2] concept

blog A case against inline agents

schoelle's picture

Context: Programs as documents

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.

blog Forthcoming language improvements

manus_eiffel's picture

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.

blog Farewell to BIT types

manus_eiffel's picture

Since the 7.0 release of EiffelStudio, BIT types are almost gone. To be precise they are not completely gone but your code will not compile out of the box if you are still using them.

blog Eiffel on Channel 9

manus_eiffel's picture

Two weeks ago I was at LANG.NEXT 2012 and was interviewed by Charles Torre to talk about Eiffel. Have a look at this 21-minute video:

blog Eiffel Design Feast

manus_eiffel's picture

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.

blog Private features

dlebansais's picture

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.

Syndicate content