Eiffel is missing from this list. Anyone fancy adding it on?

Following on from my comment in //www.eiffelroom.com/blog/colin_adams/class_fibonacci that Haskell manages integers better than we do, I extended my test program for Fibonacci numbers to make a call to a Haskell function.

Timings and output printing F(11199) (compiled with ISE 6.3) are:

Class FIBONACCI (FreeELKS) - 2ms prints: -1880045342

I was somewhat surprised to see this class in FreeELKS.

WHY? It doesn't appear to be used by anything else.

Anyway, I was rather intrigued, and gave it a try (I was interested in timing the n_th number).

I soon spotted that it was giving errors, and it was immediately obvious why. Here is a copy of the code:

<eiffel> i_th (i: INTEGER_32): INTEGER_32

I can really starting using the following appearance of EiffelStudio in my daily work, without any problems after fixing some background color issues. (post rev#75526, will be available in 6.3)

This week I have again been considering the issue of the correctness of code that receives an agent (the last time I looked at this was http://www.eiffelroom.com/blog/colin_adams/correctness_conditions_2_for_calling_an_agent).

It seems to me that the recent debate on immutable strings is misplaced. It seems related to the fact that:

• strings are not duplicated for efficiency reasons.
• since strings are mutable, it creates more aliasing than what we would care to have.

The 6.3 release of EiffelStudio will come with a new testing tool combining unit and system level testing. The tool is currently under development but is already capable of managing, creating and executing tests. At this point I would like to give a short overview on what has been implemented, how to tool is used and what functionality will be added in the upcoming weeks.

This blog entry is only for those Windows user out there. It's concerning tips and tricks for the EiffelStudio Windows Installers.

Mac fanatics out there might have heard that there is native implementation of GTK running on MacOSX. There's been a bit of backlash against the port because it doesn't provide a native MacOSX look and feel, but we are assured that they are working on it.

I was truly thrilled when I first came across exceptions in C++ after using the clumsy error reporting style of C. It made my algorithms cleaner and, therefore, it made me happy. After several years, I tried Java and I found it interesting to impose the discipline of explicitly declaring the exceptions that may be raised in a routine.