On Jan 11, 2012, at 1:04 PM, Uwe Ligges wrote:
>
>
> On 11.01.2012 18:49, Simon Urbanek wrote:
>>
>> On Jan 11, 2012, at 12:08 PM, Taylor Arnold wrote:
>>
>>> R-devel,
>>>
>>> I have noticed that making a copy of an object in R prior to using
>>> .Call on the original object can
>>> cause th
On 11.01.2012 18:49, Simon Urbanek wrote:
On Jan 11, 2012, at 12:08 PM, Taylor Arnold wrote:
R-devel,
I have noticed that making a copy of an object in R prior to using
.Call on the original object can
cause the C code to alter not only the object passed to it but also
the copy in R.
Plea
On Wed, Jan 11, 2012 at 11:49 AM, Simon Urbanek
wrote:
>
> On Jan 11, 2012, at 12:08 PM, Taylor Arnold wrote:
>
>> R-devel,
>>
>> I have noticed that making a copy of an object in R prior to using
>> .Call on the original object can
>> cause the C code to alter not only the object passed to it but
On Jan 11, 2012, at 12:08 PM, Taylor Arnold wrote:
> R-devel,
>
> I have noticed that making a copy of an object in R prior to using
> .Call on the original object can
> cause the C code to alter not only the object passed to it but also
> the copy in R.
Please see the docs - .Call does *NOT* h