TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date: Wed, 24 Jul 2002 14:26:03 -0700
Reply-To: Steven Lim <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <71C0MIYS3N2ZVSYVUQKJH62ZV521U.3d2efda7@default>
Content-Type: text/plain; charset="iso-8859-1"
From: Steven Lim <[log in to unmask]>
Parts/Attachments: text/plain (30 lines)
Than'x everyone for the useful and possible solutions to my problem... the
suggestions led me to ask Rational about the issue and it was finally

Apparently, Rational Apex Ada (the IDE and compiler I use) DO initialize my
array of record type... taking a snippet of some literature (from Rational's
Tech Support)

The Apex Ada 95 compiler generates default (implicit) initialization for
certain RECORD objects or components and all access type objects or
components - it doesn't do this for scalars or arrays (unless their
components need it or possibly if its elements are not an integral number of
bytes long). Apex Ada 95 also performs implicit initialization when a record
is tagged or has access type components (as required by RM95) or if it
contains dynamically sized components or a discriminant. This may either be
a partial initialization of just the components that require it or (often)
the entire record. Apex Ada 95 may also initialize records that have a
significant number of unused storage gaps within their layouts in order to
speed up record comparisons. The hueristics that determine when and how the
implicit initialization occurs are complex and change from release to
release of Apex.

The problem was resolved by avoiding the use of an array of records... duh!

Than'x again for everybody's help and time!