Displaying 3 results from an estimated 3 matches for "do_isvector".
2019 Jul 12
2
strange increase in the reference number
...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 reveal what was going on, at least to me) and I don't
have the time to dig super deeply into this right now, but perhaps Luke or
Tomas know why this is happening of the top of their head.
Sorry I can't be of more help.
~G
On Fri, Jul 12, 2019 at 11:4...
2019 Jul 13
0
strange increase in the reference number
...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 reveal what was going on, at least to me) and I don't
have the time to dig super deeply into this right now,? but perhaps Luke or
Tomas know why this is happening of the top of their head.
Sorry I can't be of more help.
~G
On Fri, Jul 12, 2019 at 11:4...
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