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,8201deea80f1752a X-Google-Attributes: gid103376,public From: "Steve Mossom" Subject: Re: 3-bit array porting problem from ADA83 to GreenHills ADA95 Date: 1999/11/09 Message-ID: <3827e839@pull.gecm.com>#1/1 X-Deja-AN: 546373112 References: <382386fe.85782690@news.uswest.net> X-Trace: 9 Nov 1999 09:24:09 GMT, sg2ntw50041.dsge.edinbr.gmav.gecm.com X-MSMail-Priority: Normal X-Priority: 3 Newsgroups: comp.lang.ada X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Date: 1999-11-09T00:00:00+00:00 List-Id: I haven't delt with your particular problem, however I have been working on a project porting some legacy code from XD Ada'83 to GreenHills ADA Multi. We have had numerous (too many to mention!) problems with the way the compiler handles representation clauses. It seems, from what I have read, that the ADA'95 LRM makes 'recommendations' to compiler vendors regarding their implementation in this area it does not really enforce any rules (quite rightly as it should not be implementation specific) . GreenHills response to my problems was good to a point - If the problem was allready fixed in a later issue of the compiler they would ship that to us. More recently, for issues which are not allready fixed in a later version, we have been told 'The LRM does not enforce that' and been given workarounds for our problems using 'unchecked conversion' which is not the most desirable way of doing things. Darrell Higgins wrote in message news:382386fe.85782690@news.uswest.net... > Has anybody dealt (successfully) with a port of ADA83 that contains > 3-bit arrays of enumerated types into GH ADA95? GreenHills does not > support 3-bit arrays and we are searching for techniques/solutions to > achieve this port. > Our application constrains us to keep the arrays, due to the high LOC > affected. So how about it...Trash the compiler and look for a new one? > Be kind in reply - I'm a nervous ADA newbie.