Blogs

blog EiffelStudio 7.0 released

manus_eiffel's picture

We are pleased to announce the availability of EiffelStudio 7.0.

blog Fixed sized graphics

finnianr's picture

Fixed size graphics

The irony of using fixed size graphics is that they appear as a different size depending on the users screen resolution. What I would like to be able to do is specify in my code the physical size of how graphics will appear.

blog Frameworks insult language designers

schoelle's picture

Designing a programming language is an difficult task. During my time in academia, I had the great pleasure to meet some language designers. Listening to their stories is highly educating. Things that look simple or arbitrary at first become deep insights into the way humans understand problems and model solutions. There is nothing trivial in deciding names of keywords or punctuation.

blog Type safe Eiffel (4, chapters "Generic constraints based on conformance" and "Validation with local analysis" included)

From the beginning of Eiffel the language has been characterized as strongly typed. But since its beginning there has been a hole in the type system which has not yet been fixed up to now (the so called catcall problem).


What is the hole?

The existence of the hole can be demonstrated with very simple examples.

blog Type safe Eiffel (4, chapters "Backward compatibility" and "Promiscuous generic conformance" included)

From the beginning of Eiffel the language has been characterized as strongly typed. But since its beginning there has been a hole in the type system which has not yet been fixed up to now (the so called catcall problem).


What is the hole?

The existence of the hole can be demonstrated with very simple examples.

blog Why Type-safety?

schoelle's picture

The search for a type-safe version of Eiffel is a never-ending story in the development of the Eiffel language. Recently, Helmuth Brandl has created a series of blog entries with a nice description of is needed to make Eiffel type-safe. There have been others posting blog entries (including me) and it also had been a constant topic during the ECMA process of Eiffel standardization.

Interestingly, a question that was seldom raised was: why do we need type-safety? As absurd as it seems for all the mathematicians to raise this question, the Eiffel community has understood for a long time that mathematical soundness is not a reason in itself. Instead, it serves a purpose in the enterprise of language design: giving software developers means to express themselves in ways that reduce the number of defects in his/her programs and enable him/her to master complex problems he/she would not be able to master without.

blog Type safe Eiffel (3, chapter "Covariance" included)

From the beginning of Eiffel the language has been characterized as strongly typed. But since its beginning there has been a hole in the type system which has not yet been fixed up to now (the so called catcall problem).


What is the hole?

The existence of the hole can be demonstrated with very simple examples.

blog Type safe Eiffel (2, chapter "Feature rich ANY" included)

From the beginning of Eiffel the language has been characterized as strongly typed. But since its beginning there has been a hole in the type system which has not yet been fixed up to now (the so called catcall problem).


What is the hole?

The existence of the hole can be demonstrated with very simple examples.

blog Type safe Eiffel (1)

From the beginning of Eiffel the language has been characterized as strongly typed. But since its beginning there has been a hole in the type system which has not yet been fixed up to now (the so called catcall problem).


What is the hole?

The existence of the hole can be demonstrated with very simple examples.

blog Quick benchmark on loops

ted_eiffel's picture

This is a quick benchmark result on loops: across as loop end and from untill loop end

Source Code

note
	description : "across_benchmark application root class"
	date        : "$Date$"
	revision    : "$Revision$"
 
class
	APPLICATION
 
inherit
	ARGUMENTS
 
create
	make
 
feature {NONE} -- Initialization
 
	make
			-- Run application.
		local
			l_array: ARRAYED_LIST [I