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.107.12.94 with SMTP id w91mr3253597ioi.85.1519249332859; Wed, 21 Feb 2018 13:42:12 -0800 (PST) X-Received: by 10.157.68.9 with SMTP id u9mr220631ote.5.1519249332755; Wed, 21 Feb 2018 13:42:12 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w142no385509ita.0!news-out.google.com!s63ni1248itb.0!nntp.google.com!o66no384584ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 21 Feb 2018 13:42:12 -0800 (PST) In-Reply-To: <3a2e91d4-f563-4843-9c80-5a76732626d3@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=71.171.117.31; posting-account=QF6XPQoAAABce2NyPxxDAaKdAkN6RgAf NNTP-Posting-Host: 71.171.117.31 References: <3a2e91d4-f563-4843-9c80-5a76732626d3@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: non record limited type From: Jere Injection-Date: Wed, 21 Feb 2018 21:42:12 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader02.eternal-september.org comp.lang.ada:50526 Date: 2018-02-21T13:42:12-08:00 List-Id: On Wednesday, February 21, 2018 at 10:58:18 AM UTC-5, Mehdi Saada wrote: > > Also, another question: if only the public view is limited, what about the parameter passing ? Is it by reference or copy, when such copy are made in the body ? I would guess by copy, but I prefer to ask I can't answer why on your first question, but on this one: The RM in section 6.2 specifies how parameter passing is done based on the type. http://www.ada-auth.org/standards/12rm/html/RM-6-2.html#I3382 Based on that, your limited private which is really an integer would still be a by-copy-type. I don't know the RM's intention but the wording suggests that at least. Note you can also used the "aliased" keyword in a function/procedure signature to enforce an aliased variable which will be passed by reference as well: -- Object is passed by reference procedure Do_Something(Object : aliased in out Some_Type);