[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: list separator in config entries
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-10-10 11:07:18
Message-ID: 20071010110718.GA13013 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]

On 10.10.07 06:03:39, Thomas Braxton wrote:
> On 10/10/07, Oswald Buddenhagen <ossi@kde.org> wrote:
> >
> > On Wed, Oct 10, 2007 at 04:47:45AM -0500, Thomas Braxton wrote:
> > > if KConfigGroup treats null and empty the same then how do you
> > > differentiate between an entry that was stored empty and an entry that
> > > does not exist (i.e.  deleted or never eixisted)?
> > >
> > it is one thing how you store the "deleted" state internally and another
> > how you expose it in the api. if you want to use isNull() to save an
> > additional "deleted" flag (i would do that, too), then writeEntry must
> > have a check if (val.isNull()) val = ""; or something to that effect.
> >
> Ok, I don't have a problem with that, then externally null == empty.

Thats all I was talking about actually, seems I have expressed myself
very badly :(  I'll try to do it better next time.

Andreas

-- 
Don't plan any hasty moves.  You'll be evicted soon anyway.
[prev in list] [next in list] [prev in thread] [next in thread]