[RFC] Using KPassivePopup from KSystrayIcon

[Lubos Lunak]

On čt 5. dubna 2007, Thiago Macieira wrote:
> Boyd Stephen Smith Jr. wrote:
> >Could someone in charge throw up a document on techbase that we can
> > treat as
> >canonical?  Or, should the developer.kde.org document ([1] above) be
> >treated
> >as canonical and any of 0, 0L, or NULL be acceptable across all KDE
> > code?
>
> The C++ standard requires "0" to be accepted as a pointer value,
> indicating a null pointer. Even if the architecture is weird and the
> actual value stored in the pointer isn't an actual zero.
>
> Now, what g++ does is define NULL to be a null pointer that can be cast to
> any pointer type, but won't cast to integers (afaik). So, it's "better
> than 0".
>
> I'd say we should stay with "0" until we can be sure of NULL working
> everywhere.

 Oh please. How exactly are we going to compile KDE on platforms that have so 
broken C++ implementations that they didn't get even NULL right?

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak at suse.cz , l.lunak at kde.org
Lihovarska 1060/12   tel: +420 284 028 972
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http//www.suse.cz