list separator in config entries

Thomas Braxton kde.braxton at gmail.com
Wed Oct 10 12:03:39 BST 2007


On 10/10/07, Oswald Buddenhagen <ossi at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071010/44d557bf/attachment.htm>


More information about the kde-core-devel mailing list