Fabien Costantini wrote:

> Wouldn't it be a nice thing to make the Shared image destructor protected ?

No.

First reason: it is already protected.

Second reason: that's the problem: if you use the base class pointer
and have a virtual method (here the destructor) then it _will_ be
called (remember the discussion of virtual protected draw() ?). And
the object will be deleted anyway.

Yes, I know that you know that, but this is IMHO the bad consequence
of making the destructor protected - it doesn't really help. Sigh :-(

Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to