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,2807a72eaf629c11 X-Google-Attributes: gid103376,public From: Martin Dowie Subject: Re: Apex 3.0.0b can't handle dynamic positional agregates? Date: 1999/10/14 Message-ID: <38062040.B0098EF@dowie-cs.demon.co.uk>#1/1 X-Deja-AN: 536760165 Content-Transfer-Encoding: 7bit X-NNTP-Posting-Host: dowie-cs.demon.co.uk:193.237.34.207 References: <37FE1232.EB0AD5EE@boeing.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@demon.net X-Trace: news.demon.co.uk 939925569 nnrp-11:23540 NO-IDENT dowie-cs.demon.co.uk:193.237.34.207 MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-10-14T00:00:00+00:00 List-Id: which version of Apex 3.0.0b are you using? i'm using the version for VxWorks and it is quite happy about this construct. perhaps time to call up some support... Robert Jordan wrote: > I try to compile a statement like > > stuff : stuff_type := (first, second, third, Others => Too_Many); > > But Apex 3.0.0.b comes back with an error: > > [MID] Unimplemented feature: dynamic positional aggregate with Others. > > The LRM (4.3.3) actually shows an example of this being used. Even when > I try to use the exact LRM example > > stuff : stuff_type := stuff_type'(first, second, Third, Others => > Too_Many); > > I still get the same error. > > There's lots of ways around this problem, but it's going to make my code > hard to read. I wanted the Others statement and the remaining elements > to be as compact as possible so the numerous tables I need to define are > easily maintained (One per line, columns lined up, etc...). > > Apex claims to be ADA95 compliant, so how can they have Unimplemented > features which are not related to the annexes? > > Robert