search for: refobject

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

...to tighten S4<>refClasses integration? Or it's just not a good idea to mix them as in the 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 envir...

...is happening? Thanks for any help in working around this - my datasets are just not fitting into my 4GB, 32 bit linux machine (even though my actual data size is around 800MB) Nawaaz > new.ref <- function(value = NULL) { + ref <- list(env = new.env()) + class(ref) <- "refObject" + assign("value", value, env = ref$env) + ref + } > object.size(y) [1] 587941404 > y.ref = new.ref(y) > object.size(y.ref) [1] 328 > data = list() > data$y.ref = y.ref > object.size(data) [1] 492 > save(data, "data.RData") ... run R ag...

...is happening? Thanks for any help in working around this - my datasets are just not fitting into my 4GB, 32 bit linux machine (even though my actual data size is around 800MB) Nawaaz > new.ref <- function(value = NULL) { + ref <- list(env = new.env()) + class(ref) <- "refObject" + assign("value", value, env = ref$env) + ref + } > object.size(y) [1] 587941404 > y.ref = new.ref(y) > object.size(y.ref) [1] 328 > data = list() > data$y.ref = y.ref > object.size(data) [1] 492 > save(data, "data.RData") ... run R ag...

...d the build system. This provides a new foundation for our future work on the meta structure of our code base. Tests Our limited tests have been improved and a number of unit tests has been added. This helps us improving the quality of Icecast with future releases. refobject We unified the API for several types (and more to come) with the new refobject metatype. This also allowed us to start migrating away from old refbuf to new buffer API. Module support We added a basic module support to Icecast. Currently there is no public m...