This is a quick benchmark result on loops: across as loop end and from untill loop end
description :"across_benchmark application root class"
-- Run application.local
I was working with the testing tool, writing tests and so on. When I was tired at the end of a day and running a test that would not stop at a breakpoint within 2 mins. I closed my eyes to have a small rest, waiting the breakpoint hit. At that time, I was hoping so much that EiffelStudio could alert me by any means rather than printing something on the status bar.
I did a small app to benchmark extension performance of major Eiffel list data structures on my Win32 XP machine, using EiffelStudio 22.214.171.12489, Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86, Microsoft (R) Incremental Linker Version 8.00.50727.42.
I extend [INTEGER, INTEGER] into the lists, and calculate time and memory usage (increase).
In EiffelStudio 6.2, Eiffel Information System (EIS) will be introduced. The goal of EIS is to provide a unified mechanism for linking development objects — classes and features, or even targets and groups — of Eiffel systems with external information. This term refers to information other than Eiffel program texts.
I was asked what the benefit of Exceptions as Objects (EAO) was in Eiffel. My short answer was flexibility of design. I knew that this answer was far from sufficient. Now I take the time my machine is busy running tests to think about it deeper and write it down. Hopefully people who are trying using it or starting to learn this area of Eiffel may better understand the mechanism and its benefits.