Re: Weird controlled behavior - Gnat 3.15p NT

[Dmitry A. Kazakov <mailbox@dmitry-kazakov.de>]

On Tue, 09 Sep 2003 02:01:57 GMT, Hyman Rosen <hyrosen@mail.com>
wrote:

>Robert I. Eachus wrote:
> > there are a number of situations where even a limited object
> > may be finalized several times
>
>It's important to point this out to new Ada programmers who are
>coming from C++, since this is a major difference in the languages.
>In C++, an object's constructor and destructor are called exactly
>once, so an object never needs to keep track internally if it has
>been initialized or finalized.

Really? What about this:

class Foo
{
public :
   void Surprise () { this->Foo::~Foo (); }
   virtual ~Foo ();
};

You might say that the above is rubbish. Not at all. It is a design
pattern for self-destructing objects. For instance when you
encapsulate a window to an object which destroys itself upon closing
the window. Now imagine what should happen if somebody would allocate
Foo on the stack? Access violation.

Another example is when an object is put into DLL in a shared section.
Then it will be constructed over an over again, each time a new
process maps the DLL. And not surprisingly it will be also destructed
many many times. A nice feature to fight with.

---
Both Ada and C++ have this nasty problem, namely, an ability to
explicitly call parts of constructors / destructors. It is a nightmare
for a software designer. But there are many reasons why it was made
so. Some of them are not very convincing (to me). Future generations
of OO languages will hopefully solve this better.

---
Regards,
Dmitry Kazakov
www.dmitry-kazakov.de