Thiago Macieira wrote:
> I don't see any code snippet sent to the mailing list. Could you repost
> it? I might have missed it.
Well, it is quoted in your own posting. Your answer was about "template
instantiations for exported types", but the code below isn't about
exporting - at least Jordi didn't mention it.
Anyway, here it is:
Jordi Pujol wrote:
| struct foo
| {
| int m_IntValue;
| double m_Double;
| };
| QList<struct foo> StructList;
|
| And try to compile it with VC++. It complains about qHash(foo) does not
| fit with any of the overloaded uint qHash ( ... )
I'm sure you agree, that implementing pointless qHash() methods isn't what
you want to do when using QList.
> So my recommendation is to just remove that line from qwt_valuelist.h. I
> don't see why it should be there at all. If you can remember the reason
> why it was introduced in the first place, we can discuss it.
I will remove this line - the Qwt users will tell me if there is an
environment left, where this would have been necessary.
Thanks for your advice.
> In any case, this is not a Qt issue. It's a compiler mis-feature that is
> triggered by Qwt itself.
I agree, that the compiler is to blame, but all what Qwt can avoid is to
instantiate/export a QList - but Qt can avoid, that an instantiation of
QList requires an implementation of all, what is required to instantiate a
QSet.
One question remains: what makes the problem happen with Qt 4.1, 4.2 and 4.6
but not for Qt 4.3-4.5. But this might be a mystery of the compiler
implementation.
Uwe
_______________________________________________
Qt4-preview-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback
