Re: Write Barrier: was: [Rd] function-like macros undefined

From: Simon Urbanek <>
Date: Wed 16 Mar 2005 - 18:56:37 GMT

On Mar 16, 2005, at 1:34 PM, Vadim Ogranovich wrote:

> * suppose that inside a C function I have a SEXP vector x of integers
> and I want to increment each element by one. I understand that

Please correct me if I'm wrong, but I thought that the write barrier applies to assignments of SEXP values only (from the doc: "... must be used for all assignments of SEXP pointers ..." - note it says "of", not "to"). When dealing with REAL/INTEGER, I believe it's still safe to use INTEGER(x)[0]=... IMHO that's logical, too, because primitive types have no 'age' to be inherited when using ggc.

Simon mailing list Received on Thu Mar 17 06:00:26 2005

This archive was generated by hypermail 2.1.8 : Mon 24 Oct 2005 - 22:26:30 GMT