Re: Efficiency of code generated by Ada compilers

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Tue, 10 Aug 2010 16:03:13 +0200, Elias Salomão Helou Neto  
<eshneto@gmail.com> a écrit:
> It is a pity that this post became a technical discussion on array
> indexing.
Could I, if you please, talk to Phil without your prior acknowledgment  
please ? ;)

While I understand why you reacted (not the way you do... closed  
parenthesis)

> A simple question that could be asked in a single line is:
> can Ada access arrays without range checking?
Sorry, due to a recent trouble with my news reader, I've the original post.

However, on this sentence basis, I would say: if you do not want range  
check, then just disable it in the compiler option. But be warned you will  
then be unable to catch runtime error. While there is a way to safely drop  
this compiler option: validation with SPARK checker (just tell if you need  
to learn about it).

If your matter is just about range checking, the answer is as simple as  
that.

If you use GNAT, you may insert "-gnatp" in the command line arguments.
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gnat_ugn_unw/Run_002dTime-Checks.html

If you use GNAT from the GPS environment, you may open the "Project" menu,  
then the "Edit project properties" submenu. Then choose the "Switches"  
tab, then the "Ada" tab and check the "Suppress all check" check box or  
uncheck the "Overflow check" check box.

Providing I did not fail to understand what you meant.

-- 
There is even better than a pragma Assert: a SPARK --# check.
--# check C and WhoKnowWhat and YouKnowWho;
--# assert Ada;
--  i.e. forget about previous premises which leads to conclusion
--  and start with new conclusion as premise.