Displaying 9 results from an estimated 9 matches for "namedmax".
Did you mean:
name_max
2017 Sep 02
1
Please avoid direct use of NAMED and SET_NAMED macros
..., 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 currently there is no mention of these macros in the
documentation for package writers. Of course, the explanation of
NAMED there also does not adequtely describe what it is suppose...
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
explora...
2019 Jul 13
0
strange increase in the reference number
Re ENSURE_NAMEDMAX, I am unsure but think this happens in (src/eval.c at 492):
static SEXP forcePromise(SEXP e)
{
??? if (PRVALUE(e) == R_UnboundValue) {
??? /* ... SNIP ...*/
??? val = eval(PRCODE(e), PRENV(e));
??? /* ... SNIP ...*/
??? SET_PRSEEN(e, 0);
?? ?SET_PRVALUE(e, val);
?? ?ENSURE_NAMEDMAX(val);??????????...
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
2018 Apr 23
0
R 3.5.0 is released
...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,
R_tryCatchError, and R_UnwindProtect functions.
* NAMEDMAX has been raised to 3 to allow protection of intermediate
results from (usually ill-advised) assignments in arguments to
BUILTIN functions. Package C code using SET_NAMED may need to be
revised.
DEPRECATED AND DEFUNCT:
* Sys.timezone(location = FALSE) is defunct, and is ign...
2018 Apr 23
0
R 3.5.0 is released
...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,
R_tryCatchError, and R_UnwindProtect functions.
* NAMEDMAX has been raised to 3 to allow protection of intermediate
results from (usually ill-advised) assignments in arguments to
BUILTIN functions. Package C code using SET_NAMED may need to be
revised.
DEPRECATED AND DEFUNCT:
* Sys.timezone(location = FALSE) is defunct, and is ign...
2019 Apr 26
0
R 3.6.0 is released
...on all platforms.
C-LEVEL FACILITIES:
* New pointer protection C functions R_PreserveInMSet and
R_ReleaseFromMSet have been introduced to replace UNPROTECT_PTR,
which is not safe to mix with UNPROTECT (and with
PROTECT_WITH_INDEX). Intended for use in parsers only.
* NAMEDMAX has been raised to 7 to allow further protection of
intermediate results from (usually ill-advised) assignments in
arguments to BUILTIN functions. Properly written package code
should not be affected.
* R_unif_index is now considered to be part of the C API.
* R_GetCurre...
2019 Apr 26
0
R 3.6.0 is released
...on all platforms.
C-LEVEL FACILITIES:
* New pointer protection C functions R_PreserveInMSet and
R_ReleaseFromMSet have been introduced to replace UNPROTECT_PTR,
which is not safe to mix with UNPROTECT (and with
PROTECT_WITH_INDEX). Intended for use in parsers only.
* NAMEDMAX has been raised to 7 to allow further protection of
intermediate results from (usually ill-advised) assignments in
arguments to BUILTIN functions. Properly written package code
should not be affected.
* R_unif_index is now considered to be part of the C API.
* R_GetCurre...
2019 Apr 26
0
R 3.6.0 is released
...on all platforms.
C-LEVEL FACILITIES:
* New pointer protection C functions R_PreserveInMSet and
R_ReleaseFromMSet have been introduced to replace UNPROTECT_PTR,
which is not safe to mix with UNPROTECT (and with
PROTECT_WITH_INDEX). Intended for use in parsers only.
* NAMEDMAX has been raised to 7 to allow further protection of
intermediate results from (usually ill-advised) assignments in
arguments to BUILTIN functions. Properly written package code
should not be affected.
* R_unif_index is now considered to be part of the C API.
* R_GetCurre...