From: Simon Belmont <sbelmont700@gmail.com>
Subject: Re: Building limited types through nested creator functions
Date: Mon, 6 Feb 2012 16:27:43 -0800 (PST)
Date: 2012-02-06T16:27:43-08:00 [thread overview]
Message-ID: <f7678d6e-6746-485f-a148-4f0821ffe9ed@e27g2000vbu.googlegroups.com> (raw)
In-Reply-To: 45c75d2a-02b4-40b2-b69b-04c6bf7a47a5@t2g2000yqk.googlegroups.com
On Feb 6, 7:03 pm, Adam Beneschan <a...@irvine.com> wrote:
> (2) If you want users of the package to create an Inner, and then
> create an Outer that *refers* to that same Inner (without making a
> copy), then you shouldn't object to using access types (in the private
> part).
It is basically this, and I really have no objection in using the
access type. But since Ada can do it for a public type, I was just
interested if there was some sort of official way for a private type
(which would avoid the necessary evils of lifetime control,
accessibility, etc.)
Thank you again
-sb
next prev parent reply other threads:[~2012-02-07 0:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 22:03 Building limited types through nested creator functions Simon Belmont
2012-02-06 12:44 ` Julian Leyh
2012-02-06 19:11 ` Shark8
2012-02-06 22:33 ` Simon Belmont
2012-02-07 0:03 ` Adam Beneschan
2012-02-07 0:27 ` Simon Belmont [this message]
2012-02-07 0:53 ` Adam Beneschan
2012-02-07 2:19 ` Simon Belmont
2012-02-07 9:10 ` Dmitry A. Kazakov
2012-02-07 10:58 ` Georg Bauhaus
2012-02-07 13:25 ` Dmitry A. Kazakov
2012-02-07 14:43 ` Yannick Duchêne (Hibou57)
2012-02-07 15:08 ` Dmitry A. Kazakov
2012-02-07 17:04 ` Robert A Duff
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox