Dear R-devel,
We are pleased to inform you that the R Consortium OOP Working Group
has been making progress on the S7 (formerly named R7) package and are
preparing to submit it to CRAN. The S7 package is a new OOP system
designed to be a successor to S3 and S4.
As part of that effort, the group h
Ben,
yes, by definition - non-blocking means that reads won't block and always
return immediately (the point of non-blocking). The loop below is terrible as
it will cause 100% CPU usage while it's spinning. It seems that you want to
block so why are you using non-blocking mode? select() effecti
On 2/13/2023 11:14 AM, Kevin Coombes wrote:
Chat bots are like politicians, or talking dogs. The fact that they exist
is interesting. But no same person would believe anything they say.
I think it is more appropriate to be a little less harsh, " no same
person would believe EVERYTHING they say
Hi Tomas,
Apparently, inserting some kind of socketSelect() is essential when
using non-blocking sockets and a client/erve architecture. That is at
least one thing that I have learned ;-).
In C++, between sending and requesting, I inserted a call to this function:
bool wait(int s) {
fd_set
