Re: [Rd] Custom C finalizers for .Call

2015-11-24 Thread Duncan Murdoch
On 24/11/2015 6:20 PM, Andrew Piskorski wrote: On Tue, Nov 24, 2015 at 12:10:12AM +0100, Jeroen Ooms wrote: Currently it is all to easy for package authors to introduce a memory leak or stack imbalance by calling Rf_error() or R_CheckUserInterrupt() in a way that skips over the usual cleanup st

Re: [Rd] Custom C finalizers for .Call

2015-11-24 Thread Andrew Piskorski
On Tue, Nov 24, 2015 at 12:10:12AM +0100, Jeroen Ooms wrote: > Currently it is all to easy for package authors to introduce a memory > leak or stack imbalance by calling Rf_error() or > R_CheckUserInterrupt() in a way that skips over the usual cleanup > steps. I have a more modest request: Pleas