Hi, all,
I have 2 questions about signal handling in R. Would you pls help give me
some suggestions? Many thanks!
[How to block the signal in one R function]:
If one R function hopes to be running without interrupting, how can we
avoid this?
To be more specific, for one R function "func1", it w
You seem to be assuming that Ctrl-C is the way to interrupt an R session
and that it sends a signal. Neither are true, in general, nor is there
a general way to turn off interruptibility from the R console.
You have not followed the posting guide and it may be that you are only
interested in
If readChar() reads from a connection and the specified number of bytes are
not all available, it returns with what it can find. That's as documented
(further down the help page) and it's what the low-level recv() does.
However, for a blocking connection, wouldn't it be more natural to retry
until
R-team,
The $value element of the return value of *withVisible* does not agree with
the return value of *eval* when *withVisible* is passed a variable (symbol)
containing an expression object or anonymous code/expressions which
generates an expression object when evaluated (such as calls to *parse
hi all -- this might not be the correct list for this
question/discussion, though R-help didn't seem like the correct venue,
either, so...
i'm looking for just some extra clarification of how local variables
are defined/bound, beyond the simple cases given in the Language
document.
the particular
Not anything that complicated -- your answer is in the R language
definition under 'Subset assignment' and the part in "Function calls" that
describes assignment functions.
Whenever a call is found on the left side of a `<-`, it is munged by
sticking a "<-" on the function name and pulling out the
On Aug 15, 2013, at 01:46 , Gabriel Becker wrote:
> R-team,
>
> The $value element of the return value of *withVisible* does not agree with
> the return value of *eval* when *withVisible* is passed a variable (symbol)
> containing an expression object or anonymous code/expressions which
> genera
I agree that the present behavior of withVisible is the Right Thing, but
the documentation is confusing. The documentation claims that withVisible
"evaluates an expression."
This may capture an inside view of how the .Internal function is
implemented, but is nonsense from the R user's standpoint,