Hi,
Thanks for your reply,
There are several ways in which you can make your code respond to interrupts
> properly - which one is suitable depends on your application. Probably the
> most commonly used for interfacing foreign objects is to create an external
> pointer with a finalizer - that makes sure the object is released even if
> you pass it on to R later. For memory allocated within a call you can either
> use R's transient memory allocation (see Salloc) or use the on.exit handler
> to cleanup any objects you allocated manually and left over.
>
Using R's transient memory allocation is not really an option when you use
some code, like a library, not developed for R. Moreover what about c++ and
the new operator ?
One related question: if the code is interrupted, are C++ local objects
freed ?
Otherwise it is very very complex to attack all allocated objects, moreover
it depends on where happens the interruption
Best,
Karl
[[alternative HTML version deleted]]
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
