Its a compiled/interpreted difference. At the moment a small function
like this is only compiled on the second call. That is in flux as we
tune the JIT. But we should try to get rid of the difference. I
actually prefer seeing the more specific call b() since you can get
the larger context from tra
I'm running of off the rocker/drd docker image. As soon as that updates to a
fresher version I'll run again, although given what both of you see I must have
caught some fleeting state in the particular revision I'm on.
Best regards,
B.
- Original Message -
From: Dirk Eddelbuettel
On 27 November 2016 at 13:20, Duncan Murdoch wrote:
| On 27/11/2016 11:34 AM, brodie gaslam via R-devel wrote:
| > Minor issue, but the following changed as of R3.3.2 from:
| >
| > > a <- function() b()
| > > a()
| > Error in a() : could not find function "b"
| >
| > To (at least in R
On 27/11/2016 11:34 AM, brodie gaslam via R-devel wrote:
Minor issue, but the following changed as of R3.3.2 from:
> a <- function() b()
> a()
Error in a() : could not find function "b"
To (at least in R Under development (unstable) (2016-11-20 r71670)):
Error in b() : could no
Minor issue, but the following changed as of R3.3.2 from:
> a <- function() b()
> a()
Error in a() : could not find function "b"
To (at least in R Under development (unstable) (2016-11-20 r71670)):
Error in b() : could not find function "b"
Notice the "Error in **b**() :" part.