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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,591cbead201d7f34 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!8g2000hsu.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: Prohibiting dynamic allocation for the given type Date: Thu, 20 Mar 2008 14:11:29 -0700 (PDT) Organization: http://groups.google.com Message-ID: <0bf69504-30e3-493e-ac4e-222d5ef70f0d@8g2000hsu.googlegroups.com> References: <83335709-e099-416b-9967-5ab6aa0aea11@i12g2000prf.googlegroups.com> <89ac4348-4c21-478e-b491-97bfbebfdb86@p73g2000hsd.googlegroups.com> <47e1910c$0$4754$9b4e6d93@newsspool3.arcor-online.net> NNTP-Posting-Host: 62.21.84.30 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1206047490 14115 127.0.0.1 (20 Mar 2008 21:11:30 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Thu, 20 Mar 2008 21:11:30 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: 8g2000hsu.googlegroups.com; posting-host=62.21.84.30; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; FunWebProducts),gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:20513 Date: 2008-03-20T14:11:29-07:00 List-Id: On 19 Mar, 23:17, Georg Bauhaus wrote: > Using Ada 2005, you can have some of the "how long" control. > Deriving in nested scopes will limit the objects to that > scope. Yes, but this assumes that the user of the type is also implementing it - in the same scope. I was considering the type implemented in the library and the possibility to enforce some given lifetime pattern at the use site. Deriving in nested scope requires to mix the responsibilities of "provider" and "user" and this is not possible when "provider" is a library. -- Maciej Sobczak * www.msobczak.com * www.inspirel.com