Threading issues?

Leo Franchi lfranchi at gmail.com
Sat Jan 5 03:11:05 UTC 2008


On Jan 4, 2008, at 5:31 PM, N.C. Wilson wrote:
>
>
> just as easily. If any locking is being done, it must either be in the
> constructor or the call itself, both of which are the same.  
> Unfortunately,
> the class uses internally a QExplicitelySharedDataPointer, which  
> seems to
> be undocumented in Qt4. Can anyone explain why the change is unsafe?

i can't exactly explain why, but there is an example in HACKING with a  
code sample that *should* work but doesn't, and it explains why. so  
you might want to look there.

leo
>
> Nicholas
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok




More information about the Amarok mailing list