KTimeZone API change

[David Jarvie]

There is a need to prevent KTimeZone instances being deleted while they are 
still referenced by anything. Currently, there can be thousands of KDateTime 
instances holding pointers to KTimeZone objects in some applications (e.g. 
KOrganizer), and there is no sure way of determining whether a KTimeZone is 
still being referenced before deleting it. The current situation has too much 
potential to cause obscure bugs and occasional crashes to leave as it is.

I propose to use reference counting to ensure that the KTimeZone data is only 
deleted once it is no longer used, implemented by backend classes. This 
requires API changes (patch attached) which I hope to make next Monday unless 
there are objections.

-- 
David Jarvie.
KAlarm author and maintainer.
http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tz.tar.gz
Type: application/x-tgz
Size: 19447 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070709/5ecc69a0/attachment.bin>