Eiffel in its current form is not completely type safe. Type errors (called catcalls in Eiffel speak) are possible. The compiler cannot detect these type errors. They usually trigger an exception at runtime.

These type errors are possible due to covariant redefinition of arguments and polymorphy. Both principles are very powerful in OO programming.

There are 4 deferred classes defined in ELKS to represent agents

  ROUTINE  [BASE_TYPE, OPEN_ARGS->TUPLE]
  PROCEDURE[BASE_TYPE, OPEN_ARGS->TUPLE]   
  FUNCTION [BASE_TYPE, OPEN_ARGS->TUPLE, RESULT_TYPE]
  PREDICATE[BASE_TYPE, OPEN_ARGS->TUPLE]   

The OPEN_ARGS is tuple to represent the tuple of arguments which need to be provided at call time.

I've recently been toying with the idea of ephemeral classes. An ephemeral class is a class which does not have attributes. The immediate benefits of such classes is that their features can be used for objectless calls, the same way we can access constants or external features.

Introduction

Originally Eiffel Software's object serialization was written in C and was proposing the following alternative:

• basic: the same version of the executable on a particular platform can store and retrieve objects.
• general: different versions of the executable on a particular platform can store and retrieve objects.
• independent: different versions of the ex

I'm not sure if this feature was noticed by many so I figured out I would write an entry on the matter. Starting with 6.5 we have added the notion of transient attribute to our runtime. Transient attributes are not stored to disk and thus their absence in the storable file means that they can safely be ignored upon retrieval.

It can be useful in many scenarios.

The recently floated proposal to add the `across' looping construct to Eiffel seems seriously mistaken.

Hi Eiffelroom users,

You might not have noticed, but eiffelroom.org (or .com) is now running on drupal6 (before it was drupal5). . We tried to do the best migration as possible, however if you notice any regression/bug, please let us know using the contact page.

I am so excited that I can really push ISE Eiffel compiler to support full Unicode. 6.6 should be the first version to support it.

The first thing I do is parsing UTF-8 source code.