On Thursday 11 May 2006 18:52, David Faure wrote: > On Thursday 11 May 2006 18:36, Peter Kümmel wrote: > > David Faure wrote: > > > > > > I'm confused. This file doesn't use QHash/QSet at all, so why is a QHash > > > implementation needed? > > > Is it due to some other file hashing KSortableItems? > > > > > > > Yes, compiling stops there because it couldn't find a qHash function with > > the correct argument. > > Where's "there"? I am quite confused as to why any code would try to hash > KSortableItem or KSortableList.
Ah I see the answer on kde-core-devel. Because of the stupid QList::toSet method. Ah well. Ok for a hack then. But casting a pointer to an int will break on Windows 64 bit, so better use "Q_ASSERT(0); return 0;" there. I honestly see no reason at all why someone would use a set or hash in combination with KSortableItem. -- David Faure, [EMAIL PROTECTED], sponsored by Trolltech to work on KDE, Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org). _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
