Thanks for all your input. I'll have a look at QUIP-6 and a closer
look at the implementation.
2018-07-10 23:55 GMT+02:00 Thiago Macieira :
> On Tuesday, 10 July 2018 12:31:30 PDT Lorenz Haas wrote:
>> So I wonder if there is any technical/intentional reason why there is
>> no timeout parameter?
>
On Tuesday, 10 July 2018 12:31:30 PDT Lorenz Haas wrote:
> So I wonder if there is any technical/intentional reason why there is
> no timeout parameter?
There may be. The problem with timed thread waits is that you need to wake up
and release state at the same time the signaller is trying to use
Il 10/07/2018 22:07, Lorenz Haas ha scritto:
Hi André,
you are right. My statement was not precise enough: Adding a parameter
to the existing function would be BiC, adding an overload "void
QFutureWatcher::waitForFinished(int timeout);" is BC but would be SiC
because it makes function pointers a
Hi André,
you are right. My statement was not precise enough: Adding a parameter
to the existing function would be BiC, adding an overload "void
QFutureWatcher::waitForFinished(int timeout);" is BC but would be SiC
because it makes function pointers ambiguous - at least I think so.
About the latte
Hi Lorenz,
I can only reply to the second half of your request.
Follow-up question if a timeout could be added: AFAIK adding an new
parameter to waitForFinished() or adding an overload is BiC.
That's only true if you *change* the existing method. Adding a new
overload while keeping the exist
Hi,
today I wished QFuture::waitForFinished() had a timeout parameter.
After a brief look waitForFinished() uses a QWaitCondition::wait()
internally, which already provides an optional timeout parameter.
So I wonder if there is any technical/intentional reason why there is
no timeout parameter?
