From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
Subject: Re: Task origin track from a class
Date: Wed, 13 Jul 2011 10:43:15 +0200
Date: 2011-07-13T10:43:15+02:00 [thread overview]
Message-ID: <4e1d5aa3$0$6544$9b4e6d93@newsspool4.arcor-online.net> (raw)
In-Reply-To: <13h82glc3htf0.1sjzw91gfndbf$.dlg@40tude.net>
On 7/13/11 9:41 AM, Dmitry A. Kazakov wrote:
> On Tue, 12 Jul 2011 17:36:29 -0700 (PDT), Shark8 wrote:
>
> The actual problems are:
>
> 1. The procedure of destruction of the objects having task components.
> Tasks are completed *before* Finalize is called. Ada's approach to
> construction/destruction is very much broken.
When the life time of objects is determined by Ada's
language rules (and not by the type system), isn't it
normal to expect that the language defined wrecking
ball smashes the thing only after it has finished?
What would be the alternative? Would it be that the
programmer then has to actively manage all parts of
destruction himself?
When an implementation collects garbage, when would
the "destructor" run? Do finalization and RAII destruction(?)
have to be separate things?
next prev parent reply other threads:[~2011-07-13 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 3:24 Task origin track from a class Rego, P.
2011-07-12 5:57 ` Simon Wright
2011-07-12 7:41 ` Dmitry A. Kazakov
2011-07-12 10:29 ` Simon Wright
2011-07-12 10:31 ` Simon Wright
2011-07-13 0:36 ` Shark8
2011-07-13 2:57 ` Rego, P.
2011-07-13 7:41 ` Dmitry A. Kazakov
2011-07-13 8:43 ` Georg Bauhaus [this message]
2011-07-13 11:59 ` Dmitry A. Kazakov
2011-07-13 16:31 ` Shark8
2011-07-13 17:22 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox