KConfigGroup (Re: KDE/kdelibs/khtml)

[Stephan Kulow]

Am Sonntag, 11. Februar 2007 00:11 schrieb Aaron J. Seigo:

> > I am strongly against this. People will write code like
> > KConfigGroup group1("myconfigrc","group1");
> > group1.writeEntry(..);
> > KConfigGroup group2("myconfigrc","group2");
> > group2.writeEntry(..);
> > ... which will lead to myconfigrc being parsed twice. Very slow.
>
> sorry, my assumption was that we'd be using a KSharedConfigPtr internally
> so this wouldn't be an issue.

I think this falls into the category of "convenience trap" because you make it 
easier to define a global KConfig where a KSImpleConfig would be perfect - or
you make it harder to define a read only config object than a normal one. 

On that topic: why do we still need the read only argument? Shouldn't KConfig 
know pretty well if it was changed?

Greetings, Stephan