Hi everybody, I have a question concerning the file-cycle of Rcpp::XPtr: Consider a XPtr with the default delete finalizer wrapping some pointer. If I use the copy constructor to create another XPtr, this is pointing at the same underlying object as expected. What happens if one of these pointers goes out of scope and is at some point garbage collected? Is the underlying object deleted leaving the other XPtr with a broken pointer? Or is the object protected by the existence of the other pointer? From my experiments I have the impression that the latter is the case, which would be the desired behaviour. But it would be nice if one could be sure.
Thanks Ralf _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel