Re: [Rd] Passing a large array to .Call by reference

2014-01-13 Thread Dirk Eddelbuettel
On 14 January 2014 at 02:02, Boris Aronshtam wrote: | I need to pass a large array to my C function. I am using .Call(). I can clearly see according to the memory consumption (reported by gc()) that the array is duplicated. Is there a way to avoid this duplication and pass the array by referenc

[Rd] Passing a large array to .Call by reference

2014-01-13 Thread Boris Aronshtam
I need to pass a large array to my C function. I am using .Call(). I can clearly see according to the memory consumption (reported by gc()) that the array is duplicated. Is there a way to avoid this duplication and pass the array by reference? [[alternative HTML version deleted]] ___

Re: [Rd] predict.glm line 28. Please explain

2014-01-13 Thread Gabriel Becker
Paul, These are inferences from the code you included. I didn't write and have not looked particularly closely at predict.glm... object is getting passed to predict.lm in certain situations by the code you included. This is how altering the object will affect behavior. The inner function calls ge

[Rd] predict.glm line 28. Please explain

2014-01-13 Thread Paul Johnson
I imitated predict.glm, my thing worked, now I need to revise. It would help me very much if someone would explain predict.glm line 28, which says object$na.action <- NULL # kill this for predict.lm calls I want to know 1) why does it set the object$na.action to NULL 2) what does the commen