Re: Covariance / catcall approach -- RE: standardization of ELKS

Eric Bezault wrote:
> Helmut Brandl wrote:
>   
>> your proposal in a nutshell: Let the runtime find out, if the call is 
>> valid or not.
>>
>> Actually all compilers I know of (EiffelStudio, SmartEiffel, The Eiffel 
>> Compiler, probably also the Gobo Eiffel compiler) do it that way.
>>     
>
> The Gobo compiler has two modes: either report CAT-calls at compilation
> time (using the dynamic type sets as described in ETL2), or at run-time.
> The former is the default.
>
>   
Great. I would be interested in your experience with the algorithm 
described in ETL2. I have heard that it is rather pessimistic, i.e. it 
flags many catcalls even if in reality there is no real danger of a catcall.

I have sent this message to your gobo mailing list as well, because it 
might be more appropriate to discuss it there.

By the way: In your documentation at gobosoft.com (dated march 2006) you 
described a lot of limitations of your compiler. Have you already 
overcome these limitations?

Regards
Helmut

The Eiffel Compiler: http://www.sourceforge.net/projects/tecomp
Documentation: http://tecomp.sourceforge.net



------------------------------------