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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,4bd6ca8f7a1eb225 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.16.106 with SMTP id f10mr7019957pbd.8.1322559099476; Tue, 29 Nov 2011 01:31:39 -0800 (PST) Path: lh20ni36234pbb.0!nntp.google.com!news2.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Class with task destructor Date: Tue, 29 Nov 2011 09:31:38 +0000 Organization: A noiseless patient Spider Message-ID: References: <30604696.94.1322013045135.JavaMail.geo-discussion-forums@yqzz20> <80027d05-2740-4899-b43a-514100ec9bd2@p16g2000yqd.googlegroups.com> <40710291-64ed-46b8-9106-40b7d481effd@b32g2000yqn.googlegroups.com> Mime-Version: 1.0 Injection-Info: mx04.eternal-september.org; posting-host="dFCm8HWntFqmDIilBLqEJQ"; logging-data="24707"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19wW7yY2zO3NPbE5cKeHNUxuyKKpnpIQ7k=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (darwin) Cancel-Lock: sha1:QkP63icNdp9wrW/paaSQuAkePOQ= sha1:TReb7YbjjwNK8VxXsDaNsqXiAk0= Xref: news2.google.com comp.lang.ada:14715 Content-Type: text/plain; charset=us-ascii Date: 2011-11-29T09:31:38+00:00 List-Id: "Randy Brukardt" writes: > In any case, as I said, you can't sensibly call Unchecked_Deallocation > until the task is known to have stopped (if it has discriminants). >From experience with GNAT I'd say that it's not sensible to do this ever. The language explicitly makes it an error if there are discriminants, but there are all sorts of other possibilities for things to go wrong in the underlying RTS. In our case, it meant we leaked a VxWorks TCB.