SmartEiffel

SmartEiffel was the GNU free Eiffel compiler, provided with associated tools, libraries and classes. GNU has continued to support a free license Eiffel via a new project, LibertyEiffel. The compiler translates Eiffel code either to ANSI C or Java bytecode. Hence it can be used to write programs that run on virtually any platform for which an ANSI C compiler or a Java virtual machine exist.

SmartEiffel was developed at the Lorraine Laboratory of Research in Information Technology and its Applications (LORIA), an institute affiliated to the French National Institute for Research in Computer Science and Control (INRIA), on the campus of Nancy-Université in Lorraine. SmartEiffel has seen wide use in academia.

History
The project was initiated in 1994 by the French researcher Dominique Colnet. The compiler was then called SmallEiffel, in reference to the Smalltalk language. In 1995, the compiler was able to compile itself for the first time. In 1998, on the occasion of a visit to LORIA by Richard Stallman, the project became part of the GNU Project. In December 2002, the project was renamed SmartEiffel and reached version 1.0. In September 2004, SmartEiffel reached version 2.0.

In May 2005, after divergences with the working group for the normalization of the Eiffel language, the SmartEiffel project announced that they would not implement the ECMA TC39-TG4 norm.

By version 2.2 (2006 ), the project had reportedly announced via its wiki, "we, the SmartEiffel project, consider that the Eiffel language as we know it today, now contains nearly all desirable features. Therefore, version 2.2 of SmartEiffel marks the debut of a new level of stability and corresponds to what we think of as being the true Eiffel language." The statement remains published as a foundation artifact at the wiki of a successor project, LibertyEiffel.

The Debian package was removed at around the same time, reported as neglected by its own maintainer. FreeBSD removed SmartEiffel some years later, due to lack interaction from the authors of the code, and the fact that it would not work on some architectures, though with some recommendation that others may take over the challenge of maintenance of the software.