Waldo Bastian wrote:
> 
> On Wed, 28 Jun 2000, Simon Hausmann wrote:
> > On Thu, 29 Jun 2000, CVS by waba wrote:
> > > kdelibs/khtml khtml_part.cpp,1.178,1.179
> > > Author: waba
> > > CVSROOT: /home/kde
> > > Thu Jun 29 05:11:50 UTC 2000
> > > Update of /home/kde/kdelibs/khtml
> > > cvs.kde.org hosted by sourceforge.net
> > >
> > > Modified Files:
> > >     khtml_part.cpp
> > > Log Message:
> > > WABA: Static objects are evil
> >
> > I thought these kinds of "static" objects are allowed/supported?
> 
> They are allowed/supported according to the C++ standard but not according to
> the compiler/runtime environment.

Can something be done about that in the long run (i.e. from the compiler
and/or linker side) ? Wonder how Microsoft solved that problem assuming
they ran into it, too.

What happened anyway ? Desctructors called on already freed memory ?

Harri.