On Thu, 14 Aug 2014, Michael Haupt wrote:
Hi Luke,
Am 14.08.2014 um 12:08 schrieb luke-tier...@uiowa.edu:
This is a consequence of the tricks the interpreter implementation
currently plays to do complex assignments. Compiled code works
differently:
library(compiler)
cmpfun(function() {
+
AFAIK there is not supposed to be any user level code that depends on the
existence of *tmp*, but there are knock-on effects (evaluating code in a locked
environment can succeed with byte code and fail with the interpreter, for
instance)
Peter
> On Aug 14, 2014, at 14:35, Michael Haupt wrote:
Hi Luke,
Am 14.08.2014 um 12:08 schrieb luke-tier...@uiowa.edu:
> This is a consequence of the tricks the interpreter implementation
> currently plays to do complex assignments. Compiled code works
> differently:
>
>> library(compiler)
>> cmpfun(function() {
> +x<-c(1,2)
> +x[1]<-
On Thu, 14 Aug 2014, Michael Haupt wrote:
Hello,
given that `*tmp*` is removed after a replacement, how can code like this work?
Is there some special handling for a variable named `*tmp*` when it comes to
make element assignments?
x<-c(1,2)
x[1]<-42
`*tmp*`[1]<-7 # I would expect this one
Hello,
given that `*tmp*` is removed after a replacement, how can code like this work?
Is there some special handling for a variable named `*tmp*` when it comes to
make element assignments?
> x<-c(1,2)
> x[1]<-42
> `*tmp*`[1]<-7 # I would expect this one to fail
> `*tmp*`
Error: object '*tmp*'