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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,8ff8a403110109d8
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-01-07 06:20:44 PST
Path: archiver1.google.com!postnews1.google.com!not-for-mail
From: dennison@telepath.com (Ted Dennison)
Newsgroups: comp.lang.ada
Subject: Re: Compilation induced constants in Ada code?
Date: 7 Jan 2003 06:20:44 -0800
Organization: http://groups.google.com/
Message-ID: <4519e058.0301070620.75a399e5@posting.google.com>
References: <pan.2003.01.03.11.12.02.464825@nospam.org>
 <uy961981t.fsf@nasa.gov>
NNTP-Posting-Host: 65.115.221.98
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1041949244 26681 127.0.0.1 (7 Jan 2003 14:20:44
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 7 Jan 2003 14:20:44 GMT
Xref: archiver1.google.com comp.lang.ada:32681
Date: 2003-01-07T14:20:44+00:00
List-Id: <comp.lang.ada>

Stephen Leake <Stephen.A.Leake@nasa.gov> wrote in message news:<uy961981t.fsf@nasa.gov>...
> That would require coordinating with ACT to get the change into their
> releases.

These days I think the proper thing to do, unless you have an ACT
support agreement, would be to get your change put into the gcc
baseline.