similar to: passing pointer types via .C calls

Hi, I've been developing an image analysis package based on R for a while now and I've had problems relating to garbage collection, so it with great interest that I've noticed the work done by Luke Tierney in this area, and I'd like to discuss how best to fit it into my package. I'll start with how my package is structured - an image is represented by an integer with a class

Hi, I've been using Rprintf from a shared library compiled under various unix flavour for a while now. I get a warning about Rprintf being undefined when constructing the library, but everything works OK after loading. I've also been cross compiling the same library using the mingw32 tools for a while now, but the inclusion of Rprintf seems to be messing up this process. It can't

Hi Everyone, I'm experimenting with the RDCOMServer package under R-2.0.0. I'm not having much success yet - the methods im registering do show up in the registry but I'm not able to call the using RDCOMClient from another package. I'm still attempting to diagnose my problem in other ways, but though I should check to see if there are any problems have been observed by others

Hello, I think this is a bug, although it is possible that I'm doind something silly. I want to be able to determine the argument name for variables passed to a generic print function suppose we have print.foo <- function(x, ...) { nm<-deparse(substitute(x)) cat("param name is ", nm, "\n") } d<-structure(1, class="foo") Under R-1.2.[2,3] >

Hi, I've had no luck with the combination of R-2.0.1 and Rggobi/gobi (1.1-1 and 1.0-1 beta). I've tried a default configuration of ggobi, as well as one with all the plugins enabled. I'm using RedHat 9 Linux. The problem I'm experiencing is a segmentation fault when library.dynam is called from .First.lib ggobi appears to work OK from the command line. I had an earlier

Hello everyone, I've just attempted to build R-1.4 on Compaq Tru64 (I'll enclose the text from bug.report() from R-1.3.1 at the end.) The relevant part of the log is below. Any ideas? gcc -shared -o methods.so do_substitute_direct.o methods_list_dispatch.o method_meta_data.o slot.o -L/usr/local/lib /usr/ucb/ld: Warning: Unresolved: TYPEOF Rf_error Rf_protect Rf_substitute

Hi, I've found that the default options of gcc and g77 on alpha produce an executable that suffers from floating exceptions. There seems to be a problem with the configure scripts that prevents the --with-f77 option working correctly. The configure script tests that f77 is running by attempting to compile and link a dummy program - the link step seems broken on the alpha (it doesn't like

Hi everyone, I'm thinking about breaking up a large package I have to avoid loading some of the more specialised parts when it isn't necessary. The package is dependent on shared libraries. The base one will keep all of the core stuff like constructors etc and the specialised parts will need to access these. It is obviously possible to set the "local" flag to false, however

? stato filtrato un testo allegato il cui set di caratteri non era indicato... Nome: non disponibile Url: https://stat.ethz.ch/pipermail/r-help/attachments/20070327/bc70aec5/attachment.pl

Thanks, Tomas, Luke, for the clarifications. Then, I have another question. But first, let me introduce how I ended up here, because obviously I just don't go around dyn.unloading things that I've just compiled. I was testing a package with valgrind. Everything ok, no leaks. Great. But I'm always suspicious (probably unjustifiably) of all the memory that is reported as "still

Given an externalptr object 'pool' which protects an R object 'prot': # SEXP prot = (a dynamically updated list with handles) SEXP pool = R_MakeExternalPtr(p, R_NilValue, prot); R_RegisterCFinalizerEx(pool, fin_pool, TRUE); WRE explains that 'prot' remains in existence as long as 'pool' is around. Does this also mean 'prot' still exists when the

Dear R Devel, In a thread this morning Luke Tierney mentioned that R's way of garbage collecting is going to change soon in 3.4.0. I couldn't find this info on Google but I wanted to share what I had been discussing in another forum, in case now is not too late to raise considerations which could affect the design of planned changes to R's garbage collection facilities. I ran into a

Is there some way to prevent finalizers running during a section of code? I have a package that includes R objects linked to database tables. To maintain the call-by-value semantics, tables are copied rather than modified, and the extra tables are removed by finalizers during garbage collection. However, if the garbage collection occurs in the middle of processing another SQL query (which is

Hi, I''m using Rails/AAF with Ferret 0.10.11, and my index occasionally (every few weeks, roughly) becomes corrupted. If the index is busted, until I rebuild it our users are unable to save anything. I get errors like the one below, and the save rolls back. My question is, is there any way to catch the error, and continue with the save even if the model isn''t indexed? What

Hi all, I found that the finalizer of the externalPtr is not called when R is quitting. However, manually calling GC() works fine. This behavior is observed on devel R 2020-04-02 r78142 on Win and R 3.6.3 on Ubuntu. I make a reproducible package here: https://github.com/Jiefei-Wang/example Here is the detail of how to reproduce the problem, I create a temporary file in the package root path and

With this set-up options(warn = 1) tf <- tempfile() finalizer <- function(obj) { message("finalizer") close(obj$f) } this code works ev <- new.env() ev$f <- file(tf, "w") reg.finalizer(ev, finalizer) rm(ev) gc() whereas this (reversing the order of file() and reg.finalizer()) ev <- new.env() reg.finalizer(ev, finalizer) ev$f <- file(tf,

2018-03-27 6:02 GMT+02:00 <luke-tierney at uiowa.edu>: > This has nothing to do with printing or dispatch per se. It is the > result of an internal register (R_ReturnedValue) being protected. It > gets rewritten whenever there is a jump, e.g. by an explicit return > call. So a simplified example is > > new_foo <- function() { > e <- new.env() >

Hello all, i am new to shorewall and i already have a question ;) i am running a mailserver in my dmz (or actually this will be when = evertything will be working fine with shorewall) with public ip = addresses.. i have a subnet of 8 ip addresses (255.255.255.248 mask) and = i was planning of the classic 3 nic (eth0-2) setup... the dmz should = work with proxy-arping...=20 now my quesion is

hello everyone, i sampled 100 stands at 20 restoration sites and presence of 3 different invasive plant species. i came across logistic regression trees and wonder if this is suited for my purpose - predicting presence of these problematic invasive plant species (one by one) by a set of recorded ecological / geographical parameters. i'd be glad if someone would comment on applying this

I see some code in R to attach finalizers to external pointer references (Register[C]Finalizer). Anyone have an example of how to code the finalizer? R_RegisterCFinalizer accepts a C function, but I can't see how to get it to operate on the pointer, since the pointer is not passed to the function when its called. RegisterFinalizer takes an R closure, but how is it called from R (tried