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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.200.34.167 with SMTP id f36mr3004371qta.104.1504021179816; Tue, 29 Aug 2017 08:39:39 -0700 (PDT) X-Received: by 10.36.110.87 with SMTP id w84mr108023itc.9.1504021179747; Tue, 29 Aug 2017 08:39:39 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v29no1082556qtv.0!news-out.google.com!j49ni1439qtc.1!nntp.google.com!v29no1082553qtv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 29 Aug 2017 08:39:39 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=173.71.208.22; posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf NNTP-Posting-Host: 173.71.208.22 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: procedure renames creates a primitive operation? From: Jere Injection-Date: Tue, 29 Aug 2017 15:39:39 +0000 Content-Type: text/plain; charset="UTF-8" X-Received-Body-CRC: 972564816 X-Received-Bytes: 2439 Xref: news.eternal-september.org comp.lang.ada:47832 Date: 2017-08-29T08:39:39-07:00 List-Id: I was curious if this was a bug or intended. Given the following code: *************************************************** procedure Main is package Some_Package is type Main_Type is tagged null record; package Non_Primitive_Ops is procedure Some_Op(Obj : Main_Type) is null; end Non_Primitive_Ops; -- without this line, the file correctly generates compiler errors procedure Some_Op(Obj : Main_Type) renames Non_Primitive_Ops.Some_Op; end Some_Package; Var : Some_Package.Main_Type; package Other_Package is type Derived_Type is new Some_Package.Main_Type with null record; -- Should this create a compiler error? overriding procedure Some_Op(Obj : Derived_Type) is null; end Other_Package; begin Var.Some_Op; -- Should this create a compiler error? end Main; *************************************************** I used a renames clause to bring a non primitive operation into scope (for client readability when calling the procedure). However, when I did that, it created a primitive operation. Is this correct behavior or a bug? It seems odd that a procedure created through a renames clause would be primitive, but perhaps it is intended?