From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,22d1652a85f14a1e,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-02-26 15:26:29 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: papand0pul0@yahoo.com (Papandopulo)
Newsgroups: comp.lang.ada
Subject: Speeding up Ada procedure?
Date: 26 Feb 2003 15:26:29 -0800
Organization: http://groups.google.com/
Message-ID: <1d13e1b4.0302261526.40058154@posting.google.com>
NNTP-Posting-Host: 65.59.77.25
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1046301989 16001 127.0.0.1 (26 Feb 2003 23:26:29
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 26 Feb 2003 23:26:29 GMT
Xref: archiver1.google.com comp.lang.ada:34635
Date: 2003-02-26T23:26:29+00:00
List-Id: <comp.lang.ada>

I have certain procedures dealing with
large arrays which are potential performance
bottlenecks. While they didn't cause
performance problems yet I intuitively
feel they will.

Is it a way to remove runtime array
bounds and other checks for particular
procedure ?

While Ada checks are excellent on
control-type part of program where is
a lot of logic and not much time spent
it can become deadly if massive arrays
of data are being processed.

If the procedure just takes an array and
produces an array I can be sure it's not
faulty by testing it with different size
arrays and than turning off runtime checks.

That's my rationale.

Thank you,
George