Re: [Rd] Please avoid direct use of NAMED and SET_NAMED macros

2017-09-02 Thread luke-tierney
On Sat, 2 Sep 2017, Radford Neal wrote: To allow for future changes in the way the need for duplication is detected in R internal C code, package C code should avoid direct use of NAMED,and SET_NAMED, or assumptions on the maximal value of NAMED. Use the macros MAYBE_REFERENCED, MAYBE_SHARED, an

Re: [Rd] Please avoid direct use of NAMED and SET_NAMED macros

2017-09-02 Thread Radford Neal
> To allow for future changes in the way the need for duplication is > detected in R internal C code, package C code should avoid direct > use of NAMED,and SET_NAMED, or assumptions on the maximal value > of NAMED. Use the macros MAYBE_REFERENCED, MAYBE_SHARED, and > MARK_NOT_MUTABLE instead. These

[Rd] Please avoid direct use of NAMED and SET_NAMED macros

2017-09-01 Thread luke-tierney
To allow for future changes in the way the need for duplication is detected in R internal C code, package C code should avoid direct use of NAMED,and SET_NAMED, or assumptions on the maximal value of NAMED. Use the macros MAYBE_REFERENCED, MAYBE_SHARED, and MARK_NOT_MUTABLE instead. These currentl