Re: [Rd] Return values from .Call and garbage collection

2009-01-27 Thread Jon Senior
On Tue, 27 Jan 2009 12:25:12 - "Sklyar, Oleg \(London\)" wrote: > Most likely issue is your code itself, out of range indexing, failure to > initialise all elements of the allocated structure correctly, 1 and not > 0-based indexing, use of other R variables for initialisation that > should ha

Re: [Rd] Return values from .Call and garbage collection

2009-01-27 Thread Sklyar, Oleg (London)
- R is not multithreaded (or so it was) and thus race condition cannot occur - I would think there is no call to GC at the time of assignment of the return value to a variable. GC is only called within other R calls as R as mentioned above is not multithreaded Most likely issue is your code itself

Re: [Rd] Return values from .Call and garbage collection [Additional information added]

2009-01-27 Thread Duncan Murdoch
On 27/01/2009 7:11 AM, Jon Senior wrote: Hi all, I'm posting this here as it discusses an issue with an external C library. If it would be better in R-Help, then I'll repost. I'm using an external library which I've written, which provides a large set of data (>500MB in a highly condensed for