[RFC] Using KPassivePopup from KSystrayIcon

[Thiago Macieira]

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. Or C++0x.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070405/4e445e32/attachment.sig>