On 2/26/20 14:47, Gábor Csárdi wrote:
!!! DON'T TRY THE CODE IN THIS EMAIL AT HOME !!!
Ok I'll try it at work on my boss's computer, sounds a lot safer.
H.
Well, unlink() does what it is supposed to do, so you could argue that
there is nothing wrong with it. Also, nobody would call
!!! DON'T TRY THE CODE IN THIS EMAIL AT HOME !!!
Well, unlink() does what it is supposed to do, so you could argue that
there is nothing wrong with it. Also, nobody would call unlink() on
"~", right?
The situation is not so simple, however. E.g. if you happen to have a
directory called "~", and
If people want to create a new interpreter (for R or any other
data-driven programming language), or do something closely related
(such as adapt an existing interpreter), I think a better strategy
would be to focus on real time computing.
I note that Oracle who appears to be sponsoring this
There's a patch under review:
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17595
Best,
Lionel
On 2/26/20, Kirill Müller wrote:
> Hi
>
>
> Consider the following example:
>
> f <- function(expr) g(expr)
> g <- function(expr) {
> h(expr)
> }
> h <- function(expr) {
> expr #
Hi
Consider the following example:
f <- function(expr) g(expr)
g <- function(expr) {
h(expr)
}
h <- function(expr) {
expr # evaluation happens here
i(expr)
}
i <- function(expr) {
expr # already evaluated, no costs here
invisible()
}
rprof <- tempfile()
Rprof(rprof)
f(replicate(1e2,
