One more question to kstaticdelter

[Andreas Pakulat]

On 01.05.07 14:43:29, Andreas Pakulat wrote:
> On 01.05.07 14:10:06, Ingo Klöcker wrote:
> > On Tuesday 01 May 2007 11:04, Christian Ehrlicher wrote:
> > > >> Yes, that looks like it's the best option.
> > > >>
> > > >> However, if someone calls the constructor twice, it leaks memory.
> > > >> So, something is wrong.
> > > >
> > > > The constructor is not supposed to be called directly, but only
> > > > through self().
> > >
> > > But this can't be guaranteed because the ctor is not private.
> > 
> > That seems to be a bug then.
> 
> As long as ::instance( QStringList ) stays I think thats fine.

Hmm, if kconfig_compiler creates a singleton object then none of the two
constructors are public, they are protected yes, but that is needed.

Andreas

-- 
If you can read this, you're too close.