Re: embedded or real-time project using Eiffel

llothar wrote:
> On 20 Feb., 00:00, "Emmanuel Stapf [ES]"
> <manus_no_s...@[EMAIL PROTECTED]
> wrote:
>> I'm not sure what is not working with EiffelStudio in the area of
signal
>> handling as we do support signals, they are just transformed into
>> exceptions. And if you want to ignore a signal you have the
UNIX_SIGNALS
>> class for that (although called UNIX it works on Windows but with a
>> restricted set of signals).
> 
> Okay but is it possible to write signal handlers in eiffel?

At the moment, no because signals are mapped to exceptions. So if you 
want to program your code so that once the signal processing is done you 
simply continue the execution, then you need to design your Eiffel code 
with the proper set of rescue clauses that will help you achieve this.

> This is really expensive in many cases and impossible for a compiler
> to figure out
> so there has to be an annotation. It was not specified in Eiffel for
> one very simple reason: It was just not on the agenda.

I'm not sure what is expensive. The default should be `volatile' and 
then the optimization is to put things in register. Eiffel agenda is 
that of a coherent memory model where programmers don't get gotchas, so 
this is why the discussion doesn't need to take place.

> If i see how SCOOP took people in talking about things without any
> real programmers
> life relevance i know why the whole multithreading is not done well
> and why i had to patch my own smalleiffel version.

I'm not sure what SCOOP has to do with that, but EiffelStudio had a 
consistent multithreading implementation since it was first introduced 
in 1997. The model changed over the years but it is working great and 
many applications are benefiting from it.

Manu