From kde-core-devel  Thu Jan 05 16:09:39 2006
From: Nicolas Goutte <nicolasg () snafu ! de>
Date: Thu, 05 Jan 2006 16:09:39 +0000
To: kde-core-devel
Subject: Re: KDE/kdebase/kicker/kicker
Message-Id: <200601051709.39241.nicolasg () snafu ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113647766705462
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-00=_DTUvDIVjVDbi0ND"


--Boundary-00=_DTUvDIVjVDbi0ND
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Wednesday 04 January 2006 22:29, David Faure wrote:
> On Wednesday 04 January 2006 19:31, Chusslove Illich wrote:
> > > [: Alexander Neundorf :]
> > > I mean, I don't want to go through the whole svn and commit changes if
> > > there is something different going here.
> >
> > I'd just like to comment that Laurent Montel (mlaurent) seems to had been
> > going through kdelibs two days ago and converting in the opposite way,
> > from QString::null to QString()...
>
> We know that, this is what made the unexpected gcc-3.2.3 behavior appear.
>
> So - anyone with 3.3 to test this?

Sorry I cannot test with Qt4/KDE4, but I can compile the attached program with
Qt3 while compiling with gcc 3.3.1 (-SuSE 9.0).

Have a nice day!

--Boundary-00=_DTUvDIVjVDbi0ND
Content-Type: text/x-c++src;
  charset="utf-8";
  name="test.cpp"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="test.cpp"

#include <qstring.h>

QString test(const QString& str)
{
   return str;
}

int main(void)
{
   test(QString());
   test(QString::null);
}

--Boundary-00=_DTUvDIVjVDbi0ND--