KConfig::addConfigSources is broken

[Aaron J. Seigo]

On Sunday 18 November 2007, Thomas Braxton wrote:
> On 11/18/07, Aaron J. Seigo <aseigo at kde.org> wrote:
> > On Sunday 18 November 2007, Thomas Braxton wrote:
> > > On 11/18/07, Aaron J. Seigo <aseigo at kde.org> wrote:
> > > > and when Name is set to Bar it will write that value out to
> > > > d->developerTempFile?
> > >
> > > yes :)
> >
> > how exactly does it determine the read order?
>
> any files set with addConfigSources are treated as "defaults"
> therefore they are read before the file name passed to the
> constructor.

huh. well, suffice it to say that this is unexpected behaviour as it doesn't 
match the rest of the kconfig's read/write symmetry pattern. i suppose that's 
why the earlier implementation did it the other way around. *shrug*

if it were up to me i'd suggest that preserving that pattern is more important 
than a new concept of "most specific" where writing is no longer tied to read 
order.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071118/fbe4bb28/attachment.sig>