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

List:       kmail-devel
Subject:    Huston, we have a problem: Q_UINT32 vs. unsigned long
From:       Karl-Heinz Zimmer <khz () kde ! org>
Date:       2004-06-21 15:10:26
Message-ID: 200406211710.28448 () postmaster ! bugcops ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

just found that we are using a Q_UINT32 as return value of

     MessageProperty::serialChache()

while we are using a simple "unsigned int" as parameter in nearly
all of the messages working with the serNum, e.g. in

     KMMsgBase::getSerNum()

and in many more of them.

Sad to say I am in a terrible hurry to match a deadline so there is
no chance I can dig into the code to trace all ways the serial numbers
go and adjust them accordingly.

But still: The issue is dangerous, it may break on 64bit machines.

Who is able and has the time to solve this issue?

Karl-Heinz
- -- 
Karl-Heinz         <mailto:khz@indeview.org>        <mailto:khz@kde.org>
  Zimmer                I n d e V i e w                    K D E
  Föhren       Presentations Beyond Limitations     Conquer your Desktop
www.fiehr.de            www.indeview.org                www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFA1vpiCcaVnbvggDcRAp1yAJ40y6knh/4jd2Utwe5qFEphDMmHzACfTty9
zaxSJ3Za8CsYnirzbHgIgFE=
=cbri
-----END PGP SIGNATURE-----

_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel

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