I want to implement a time out feature in C++.
If the user does not input the value within 2 seconds then the program must display the time-out statement and ask the input again
EX(OUTPUT SCREEN):
Timer=0;
Please enter the input: //if input is not given within 2 seconds then
Time-out: 2 seconds
Timer again set to 0
Please enter the input: //if input is not given within 2 seconds then
Time-out: 2 seconds
Timer again set to 0
Please enter the input:22
Data accepted
Terminate the program`
Code:
#include<iostream>
#include<time.h>
using namespace std;
int main()
{
clock_t endwait;
endwait = 2000 ;
cout<<endwait;
while (clock() < endwait)
{
cout<<"Please enter the input:";
}
return 0;
}
I have worked on the above code. But this happens only while entering the WHILE loop. How shall i do it in a way so that, I get the required output.
I am afraid, it is not possible in a standard way because I/O operations will block, by default, the calling process until it's finalized or an error is encountered.
You could work it around by creating a thread which checks whether the input has been completed and go sleeping, if needed. But that's not really practical.
The issue lies in the abstraction
iostream
/FILE
s give you: you don't have access to the underlying source, the one the OS "understands" as well and therefore capable to give you that kind of functionality (namely, I/O polling).Output:
A separate thread is not enough, because the console read function is still running after the timeout occurs.
On POSIX you could set a timer which produces a signal and causes the read to fail with
-EINTR
.On Windows you can implement low-level console I/O timeouts with
ReadConsoleInput
andWaitForSingleObject
... but then you need to do your own line-buffering.Another idea would be to use
ReadFile
inOVERLAPPED
mode and wait on the completion event with a timeout, but that doesn't work for consoles, see Using overlapped IO for console input?Finally, new Windows versions (Vista and later) allow you to overcome the "blocking read is not cancelled by timeout" problem using
CancelIoEx
. If you call that from a separate thread, it will triggerReadFile
to return early; you won't have to implement line-buffering yourself.I think there is no need to use complex code (multithreading or mutex) for this purpose. See the code below :
I have used kbhit() function to solve your problem. The code is as follows:-