Skip to content
Prev 48599 / 63424 Next
Original Raw

arguments to .Call(), .External should be read-only?

Dirk Eddelbuettel 
It's one of my favourite Rcpp puzzles:

R> cppFunction('bool foo(NumericVector x) { x = 2 * x; return(true); }')
R> x <- 1:4                     # note that x is now an int vector
R> foo(x)                       # so this casts to numeric --> copy 
[1] TRUE
R> x
[1] 1 2 3 4                     # still the same
R> x <- 1:4 * 1.0               # BUT now we create a numeric vector
R> foo(x)
[1] TRUE
R> x                            # and that one DOES get modified
[1] 2 4 6 8
R> 

Morale: The P in SEXP means that you get to change the external object.  So
as Duncan and the WRE manual say: proceed with some caution.

Dirk

Thread (3 messages)

Greg Minshall arguments to .Call(), .External should be read-only? Jul 8 Duncan Murdoch arguments to .Call(), .External should be read-only? Jul 8 Dirk Eddelbuettel arguments to .Call(), .External should be read-only? Jul 8