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=0.7 required=5.0 tests=BAYES_00,MSGID_RANDY
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9ab76c2183ecc054
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-01-01 16:02:05 PST
Path: 
 supernews.google.com!sn-xit-03!supernews.com!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!nntp2.deja.com!nnrp1.deja.com!not-for-mail
From: Robert Dewar <robert_dewar@my-deja.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada to C Translator
Date: Mon, 01 Jan 2001 23:49:22 GMT
Organization: Deja.com
Message-ID: <92r522$ntl$1@nnrp1.deja.com>
References: <92fk1v0cou@drn.newsguy.com> <92fqlt$h8d$1@nnrp1.deja.com>
 <3A4CF58B.A8FF223C@collins.rockwell.com> <alpl29.aph.ln@leia>
 <92qfj7$7l9$1@nnrp1.deja.com> <n12r29.qrv.ln@leia>
NNTP-Posting-Host: 205.232.38.14
X-Article-Creation-Date: Mon Jan 01 23:49:22 2001 GMT
X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; U)
X-Http-Proxy: 1.0 x66.deja.com:80 (Squid/1.1.22) for client 205.232.38.14
X-MyDeja-Info: XMYDJUIDrobert_dewar
Xref: supernews.google.com comp.lang.ada:3534
Date: 2001-01-01T23:49:22+00:00
List-Id: <comp.lang.ada>

In article <n12r29.qrv.ln@leia>,
  Frode =?ISO-8859-1?Q?Tenneb=F8?= <frodet@nvg.org> wrote:
> Does the time of posting give ANY leniancy? :)

Sure, we will count it as a post from last year, and start the
new year afresh :-)

> Actually, half the time was spent on two
> part-systems (out of app. 30) with rather nasty circular
> dependencies.

Well you probably don't mean circular dependencies, since these
are illegal in Ada 83 and Ada 95, but more likely you mean code
where the elaboration is in a mess, due to serious bugs of
missing pragma Elaborate's. This is not uncommon, and can
indeed be a pain.

That's why we recommend that all new Ada applications use the
GNAT static elaboration approach to avoid this in the future
(and why we make it the default, so incompetent programmers who
don't know what they are doing in this area will accidentally
do the right thing :-)

But of course for many existing legacy applications with
confused elaboration situations, the use of the default static
elaboration mechanism is infeasible.

It is amazing how much of our support effort is spent in
helping people navigate around elaboration problems that are
really bugs in the original code. This is definitely a weak
spot in the design of Ada, I am sorry we could not fix it for
Ada 95, but there just was not enough time.


Sent via Deja.com
http://www.deja.com/