Skip to content
Prev 2451 / 63424 Next
Original Raw

Advice interfacing to an imaging library

Balasubramanian Narasimhan 
Richard> 2) garbage collection. It is now easy to lose track of
    Richard> memory, and this is likely to be significant because
    Richard> images are usually quite big. There is a delete function
    Richard> in the library, so it is possible to dispose of images
    Richard> manually, but an automated method would be nice. One
    Richard> option is to keep a global list of all pointers returned
    Richard> from C function calls, generate a list of all image class
    Richard> objects visible in R and compare the two. Any pointers
    Richard> not on the image class list can be disposed. Does anyone
    Richard> have any other ideas?

I'd look to embed a JVM into R and use all the power of Java for image
processing and garbage collection. I've done it with xlispstat but not
with R.
________________________________________________________________
B. Narasimhan                            naras@stat.stanford.edu
                             http://www-stat.stanford.edu/~naras





-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._

Thread (2 messages)

Richard Beare Advice interfacing to an imaging library Aug 2 Balasubramanian Narasimhan Advice interfacing to an imaging library Aug 2