- as long as the rest of KComponentData is not threadsafe there's IMHO no reason to use an atomic refcount
- add logic between KComponentData and KSharedConfigPtr to delete itself when both of their refcounts have reached 1
- reenable the KLocale hack
- KConfig keeps a KComponentData object and uses KStandardDirs from that object instead of KGlobal::dirs()
- added KSharedConfigPtr (inherits KSharedPtr<KSharedConfig>) for special refcount handling with KComponentData
- make KSharedPtr::d protected instead of private for KSharedConfigPtr