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

List:       kde-devel
Subject:    Re: kdelibs/kdecore
From:       <pbrown () redhat ! com>
Date:       1999-05-27 0:55:20
[Download RAW message or body]

On Thu, 27 May 1999, Mosfet wrote:

> On Mon, 26 Oct 1998, Harri Porten wrote:
> > CVS by pbrown wrote:
> > > 
> > > kdelibs/kdecore kconfig.h,1.14,1.15
> > > Author: pbrown
> > > CVSROOT: /home/kde
> > > Wed May 26 21:58:11 MET DST 1999
> > > Update of /home/kde/kdelibs/kdecore
> > > In directory zeus:/tmp/cvs-serv13729
> > > 
> > > Modified Files:
> > >         kconfig.h
> > > Log Message:
> > > hasKey() returns false if the key's value is null.
> > 
> > I used hasKey() in the past. After some QString'ing I probably can do
> > without it and it was a hack anyway but this change will break the
> > usage: There is no way to distinguish between a missing key and an empty
> > string ("key=") anymore.
> > 
> 
> That was the original behavior.

I don't know how to simulate the original behaviour when storing QStrings.
isEmpty() vs isNull()?

---
  Preston Brown                                    Systems Engineer
  pbrown@redhat.com                                Red Hat Software, Inc. 

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