[RFC] KConfig API stuff

[Oswald Buddenhagen]

On Tue, Oct 23, 2007 at 03:24:56PM +0200, David Faure wrote:
> > no, otherwise the old name rollback() would fit. ;)
> I never had a problem with the old name :-)
> 
well, no, because you didn't understand what it does. :-P

> > it sort of fits reverting the add of a new file - afterwards the file is
> > still there, but not known to svn any more. however, i never would see
> > this parallel if not pointed to.
> 
> It sounds like I don't understand what this method does then.
>
indeed. :-(

> Isn't about
>  group.writeEntry(...);
>  group.writeEntry(...);
>  group.writeEntry(...);
>  group.writeEntry(...);
>  // oh wait this was no good, revert
>  config.revert()
> ?
> 
as i tried to point out two times already (after being enlightened by
thomas), this is *not* what this function does.

as summarized in the other mail by maelcum, the use cases can be reduced
to:
- markAsClean() + reparseConfiguration(), i.e. an actual
  rollback/revert/reset/call-me-what-you-will
- markAsClean() + destruct (usually called in the parent object's d'tor)

the latter is sort of just an optimized version of the former - if one
wanted to, one could have only a rollback() with lazy reload semantics -
dunno if i could conjure it up as fast as needed.

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.