search for: cpulimitvalue

...s_pending) onintr(); - which is Windows specific and could be another important difference between Windows and Unix. This function is defined in: * src/main/errors.c (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) The do_setTimeLimit() function controls global variables cpuLimitValue and elapsedLimitValue, which are checked in R_ProcessEvents(), but other than setting the timeout limits I don't think it's involved in the runtime checks. The do_setTimeLimit() is defined in: * src/main/sysutils.c (https://github.com/wch/r-source/blob/trunk/src/main/sysutils.c#L1692-L1736...

...e another important difference between Windows and Unix. This >> function is defined in: >> >> * src/main/errors.c >> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >> >> >> The do_setTimeLimit() function controls global variables cpuLimitValue >> and elapsedLimitValue, which are checked in R_ProcessEvents(), but >> other than setting the timeout limits I don't think it's involved in >> the runtime checks. The do_setTimeLimit() is defined in: >> >> * src/main/sysutils.c >> (https://github.com/wc...

...specific and > could be another important difference between Windows and Unix. This > function is defined in: > > * src/main/errors.c > (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) > > > The do_setTimeLimit() function controls global variables cpuLimitValue > and elapsedLimitValue, which are checked in R_ProcessEvents(), but > other than setting the timeout limits I don't think it's involved in > the runtime checks. The do_setTimeLimit() is defined in: > > * src/main/sysutils.c > (https://github.com/wch/r-source/blob/trunk/s...

...This >>>> function is defined in: >>>> >>>> * src/main/errors.c >>>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >>>> >>>> >>>> The do_setTimeLimit() function controls global variables cpuLimitValue >>>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but >>>> other than setting the timeout limits I don't think it's involved in >>>> the runtime checks. The do_setTimeLimit() is defined in: >>>> >>>> * src/main/sy...

...ce between Windows and Unix. This >>> function is defined in: >>> >>> * src/main/errors.c >>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >>> >>> >>> The do_setTimeLimit() function controls global variables cpuLimitValue >>> and elapsedLimitValue, which are checked in R_ProcessEvents(), but >>> other than setting the timeout limits I don't think it's involved in >>> the runtime checks. The do_setTimeLimit() is defined in: >>> >>> * src/main/sysutils.c >>&gt...

setTimeLimit(elapsed=1) causes a timeout error whenever a call takes more than one second. For instance, this is how it works on Windows (R 3.3.1): > setTimeLimit(elapsed=1) > Sys.sleep(10); message("done") Error in Sys.sleep(10) : reached elapsed time limit Also, the error propagates immediately and causes an interrupt after ~1 second; > system.time({ Sys.sleep(10);