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,c30642befcd7bf85
X-Google-Attributes: gid103376,public
From: Ken Garlington <GarlingtonKE@lmtas.lmco.com>
Subject: Re: New GNAT ports (was Re: Ada and Automotive Industry)
Date: 1997/01/07
Message-ID: <32D2B847.6A7@lmtas.lmco.com>#1/1
X-Deja-AN: 208347058
references: <dewar.851455793@merv> <5asvku$jtu$1@goanna.cs.rmit.edu.au>
content-type: text/plain; charset=us-ascii
organization: Lockheed Martin Tactical Aircraft Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 3.01 (Win95; U)
Date: 1997-01-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Richard A. O'Keefe wrote:
> 
> [%] The pragma is
>         pragma Origin(non-negative constant integer expression);
>     saying that the first byte of the textually following statement
>     is to be at the given address.  That was the only thing I saw in
>     the 8051 book I was reading that I couldn't do in a reasonable
>     Ada subset.

Couldn't this be handled via a combination of existing Ada support
(address
clauses, etc.) plus linker support? That's the way we usually handle
it with the MIL-STD-1750. I don't know if you want to specify origins
for
random code; usually, it's for a logically related set of
code/data/literals,
or for a specific object.

--
LMTAS - The Fighter Enterprise - "Our Brand Means Quality"
For job listings, other info: http://www.lmtas.com or
http://www.lmco.com