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.182.243.226 with SMTP id xb2mr1658569obc.50.1438335087175; Fri, 31 Jul 2015 02:31:27 -0700 (PDT) X-Received: by 10.140.32.74 with SMTP id g68mr13754qgg.37.1438335087150; Fri, 31 Jul 2015 02:31:27 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!f3no5329222igg.0!news-out.google.com!78ni976qge.1!nntp.google.com!z61no4360720qge.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 31 Jul 2015 02:31:26 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=81.203.145.32; posting-account=AFCLjAoAAABJAOf_HjgEEEi3ty-lG5m2 NNTP-Posting-Host: 81.203.145.32 References: <2df4698f-4c8e-457c-822d-209cb2f8ab5e@googlegroups.com> <014427b1-ff7a-4a69-82e6-0330af77ed96@googlegroups.com> <91f88d79-197c-419f-84a8-908e05967a2c@googlegroups.com> <135c2b00-d13c-4f5d-a586-8aca442d363b@googlegroups.com> <87380683vc.fsf@adaheads.sparre-andersen.dk> <347c6be9-c918-4bc0-9494-c93cd6740def@googlegroups.com> <4cb32c40-f659-490d-bbb6-73585fc069e8@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Running a preprocessor from GPS? From: EGarrulo Injection-Date: Fri, 31 Jul 2015 09:31:27 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:27259 Date: 2015-07-31T02:31:26-07:00 List-Id: On Friday, July 31, 2015 at 11:13:21 AM UTC+2, Dmitry A. Kazakov wrote: > Soft/weak reference/pointer is a pointer that does not prevent collection, > but itself becomes invalid if collection occurs. [To access the target, a > strong pointer is obtained from the weak pointer, the object is accessed > through it, and then the strong pointer is disposed.] > [...] > Yes, there exist many implementations in Ada *and* there is no reason to > have it in the language, as it can be implemented at the library level. Many? Do you mean many libraries that implement "shared/weak pointer" semantics? Because I only know of GNATCOLL.Refcount, but this library requires you "to create a new tagged type that extends GNATCOLL.Refcount.Refcounted, so that it has a counter." This can be impractical. Apparently, the next version of GNATCOLL will include an alternative implementation[1] that removes this requirement. But this means that right now there is GNATCOLL.Refcount only. -- [1] http://www.adacore.com/developers/development-log/NF-18-O422-013-gnatcoll/