On Friday, 4 de November de 2011 21:01:30 Andre Somers wrote: > Me too. My point was, that we have slightly different patters for > basically the same sort of thing in different places in Qt. QFuture is > currently coupled with QtConcurrent, but is there a strong reason why > is must be? I was not privy to that IRC chat, perhaps you could tell us > the reasoning why it would not be possible?
There's no reason why it has to be coupled with Concurrent. Or, to put in
other words, it could be changed to work without Concurrent.
However, the problem is, it is currently too tightly coupled with
QtConcurrent. Unless someone is volunteering to do this work right now...
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
