Displaying 5 results from an estimated 5 matches for "refobjects".
Did you mean:
refobject
2001 Oct 02
2
Avoiding deep copies
Is it correct that there is no way of avoiding deep copying
of data structures? Or asked from a different perspective,
is it true that there are no pointers? :)
(not that I am a fan of pointer, they just let me
decide when to do deep copy on my own when the
memory manager doesnt do it for me :) )
I was considering writing code in R that would need
the internal representation of complex graph
2010 Oct 23
1
Plans for tighter integration of reference classes in R.
...e above example?
Second, R core integration (this bothers me much more):
> X$methods(m = function(t) a*t)
> environment(x$m)
<environment: 059bf6a4>
environment(..) does not return the refObject but the basic type. I assume that
it is the same with other core functionality. Usage of refObjects as parent.env
is also probably precluded in the similar way (don't have a patched R, so can
not test yet).
Would it be possible, some day, to use refObjects as parent.env or function's
environment without "loosing the class"?
Parenthetically, the attributes of an object (includ...
2005 Feb 24
1
Do environments make copies?
I am using environments to avoid making copies (by keeping references).
But it seems like there is a hidden copy going on somewhere - for
example in the code fragment below, I am creating a reference to "y"
(of size 500MB) and storing the reference in object "data". But when I
save "data" and then restore it in another R session, gc() claims it is
using twice the
2005 Feb 24
1
Do environments make copies?
I am using environments to avoid making copies (by keeping references).
But it seems like there is a hidden copy going on somewhere - for
example in the code fragment below, I am creating a reference to "y"
(of size 500MB) and storing the reference in object "data". But when I
save "data" and then restore it in another R session, gc() claims it is
using twice the
2018 Sep 28
0
About current Icecast development -- developer edition
Good afternoon,
earlier today I wrote a mail to the user mailing list about current
status of the current development. As pointed out by Mr. Rücker, it
seems to be good to also write to this list with a bit more technical
details.
Please note that this mail represents current master branch ("2.5.x").
We do recommend to use current stable branch ("2.4.x") for production.