Re: where exactly c++,c fail and Ada gets thru'

[Maciej Sobczak <no.spam@no.spam.com>]

Martin Krischik wrote:

> But it is the callers responsibility to check the input parameter before
> calling the function.

Of course - and it's where the code inlining can be useful. The biggest 
advantage of inlining is not in removing function call/return stuff, but 
in putting together things that otherwise could not be analysed together.

We could now start endless debate on the cases where you can or cannot 
have code inlining, but the whole point in optimization is that there 
are many ways to do it (including global program optimization, things 
like JIT and so on) - and, as already said, it's where compiler vendors 
compete. It's easier to optimize languages that have richer type 
information (and again - nobody questions that), but at the end of the 
day it's only the sequence of *observable behaviours* that is of 
interest to the programmer and everything else is left at the mercy of 
the optimizer - in this light, range checking is one of those things 
that are relatively easy to optimize.


-- 
Maciej Sobczak : http://www.msobczak.com/
Programming    : http://www.msobczak.com/prog/