Displaying 7 results from an estimated 7 matches for "mark_not_mutable".
2017 Sep 02
1
Please avoid direct use of NAMED and SET_NAMED macros
> 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 currently correspond to
>
> MAYBE_REFERENCED(x): NAMED(x) > 0
> MAYBE_SHARED(x): NAMED(x) > 1
> MARK_NOT_MUTABLE(x): SET_NAMED(c, NAMEDMAX)
>
> Best,
>
> luke
Checking https://cran.r-project.org/doc/manuals/r-release/R-exts.html
shows that...
2019 Jul 12
2
strange increase in the reference number
Hi Jiefei and Duncan,
I suspect what is likely happening is that one of ENSURE_NAMEDMAX or
MARK_NOT_MUTABLE are being hit for x. These used to set named to 3, but now
set it to 7 (ie the previous and current NAMEDMAX value, respectively).
Because these are macros rather than C functions, its not easy to figure
out why one of them is being invoked from do_isvector (a cursory
exploration didn't reve...
2019 Jul 13
0
strange increase in the reference number
...ion of `eval` works so I could be completely wrong.
B.
PS: line references are in r-devel at 76287.
On Friday, July 12, 2019, 4:38:06 PM EDT, Gabriel Becker <gabembecker at gmail.com> wrote:
Hi Jiefei and Duncan,
I suspect what is likely happening is that one of? ENSURE_NAMEDMAX or
MARK_NOT_MUTABLE are being hit for x. These used to set named to 3, but now
set it to 7 (ie the previous and current NAMEDMAX? value, respectively).
Because these are macros rather than C functions, its not easy to figure
out why one of them is being invoked from do_isvector? (a cursory
exploration didn't reve...
2019 Jul 12
3
strange increase in the reference number
Hi,
I just found a strange increase in the reference number and I'm wondering
if there is any reason for it, here is the code.
> a=c(1,2,3)
> .Internal(inspect(a))
@0x000000001bf0b9b0 14 REALSXP g0c3 [NAM(1)] (len=3, tl=0) 1,2,3
> is.vector(a)
[1] TRUE
> .Internal(inspect(a))
@0x000000001bf0b9b0 14 REALSXP g0c3 [NAM(7)] (len=3, tl=0) 1,2,3
The variable *a* initially has one
2019 Jul 19
2
ALTREP wrappers and factors
Hi Jiefei and Kylie,
Great to see people engaging with the ALTREP framework and identifying
places we may need more tooling. Comments inline.
On Thu, Jul 18, 2019 at 12:22 PM King Jiefei <szwjf08 at gmail.com> wrote:
>
> If that is the case and you are 100% sure the reference number should be 1
> for your variable *y*, my solution is to call *SET_NAMED *in C++ to reset
> the
2018 Apr 23
0
R 3.5.0 is released
...(e.g., -std=gnu++11 for the C++11 compiler).
Previously this was not done in a few cases where the default
standard passed the tests made (e.g. clang 6.0.0 for C++11).
C-LEVEL FACILITIES:
* 'Writing R Extensions' documents macros MAYBE_REFERENCED,
MAYBE_SHARED and MARK_NOT_MUTABLE that should be used by package
C code instead NAMED or SET_NAMED.
* The object header layout has been changed to support merging the
ALTREP branch. This requires re-installing packages that use
compiled code.
* 'Writing R Extensions' now documents the R_tryCatch,...
2018 Apr 23
0
R 3.5.0 is released
...(e.g., -std=gnu++11 for the C++11 compiler).
Previously this was not done in a few cases where the default
standard passed the tests made (e.g. clang 6.0.0 for C++11).
C-LEVEL FACILITIES:
* 'Writing R Extensions' documents macros MAYBE_REFERENCED,
MAYBE_SHARED and MARK_NOT_MUTABLE that should be used by package
C code instead NAMED or SET_NAMED.
* The object header layout has been changed to support merging the
ALTREP branch. This requires re-installing packages that use
compiled code.
* 'Writing R Extensions' now documents the R_tryCatch,...