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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,e977cd3ab4e49fef
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Question about record rep spec placement
Date: 1997/01/17
Message-ID: <E45u99.35q@world.std.com>#1/1
X-Deja-AN: 210549562
references: <32DCFDAA.2656@lmtas.lmco.com> <32DD307D.7208@watson.ibm.com>
 <32DE3FAD.17A1@lmtas.lmco.com>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1997-01-17T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <32DE3FAD.17A1@lmtas.lmco.com>,
Ken Garlington  <GarlingtonKE@lmtas.lmco.com> wrote:
>We will check to see if this is the case. Is there a complete list of
>cases
>related to freezing occurences that are different between Ada83 and Ada?

Incompatibilities are documented in the AARM.  Look at section 13.14,
for lots of verbiage about forcing/freezing.

However, I should warn you that the Ada 83 rules did not make perfect
sense to me when I wrote the AARM stuff, so the AARM list of differences
is probably incomplete.  How can you make a list of differences between
two sets of rules, when you can't quite understand one set of rules?
Note that the Ada 83 rules officially include the AI's.

In any case, I'm pretty sure that the upward incompatibilities exist
only for extremely obscure cases.  Why don't you post your code (or a
boiled-down version of it)?  Any decent compiler will tell you which
freezing occurrence is causing the trouble, so it shouldn't be hard to
track this down.  I will be surprised if you've run into an upward
incompatibility -- most likely one or the other compiler has a bug.

- Bob