[Rd] Suggestion: Custom filename patterns for non-Sweave vignettes

2013-02-14 Thread Henrik Bengtsson
Hi, as far as I understand it, the new R devel feature of processing non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or ".Rmd" files, (b) check for a registered vignette engine, (c) process the file using the registered "weave" function, (d) and possibly post process the generated we

Re: [Rd] stopping finalizers

2013-02-14 Thread Hadley Wickham
> There are R objects representing survey data sets, with the data stored in > a database table. The subset() method, when applied to these objects, > creates a new table indicating which rows of the data table are in the > subset -- we don't modify the original table, because that breaks the > ca

[Rd] Error: 'mcMap' is not an exported object from 'namespace:parallel'

2013-02-14 Thread Cook, Malcolm
> library(parallel) > mcMap(identity,1:5) Error: could not find function "mcMap" > parallel:::mcMap(identity,1:5) [[1]] [1] 1 [[2]] [1] 2 [[3]] [1] 3 [[4]] [1] 4 [[5]] [1] 5 > parallel::mcMap(identity,1:5) Error: 'mcMap' is not an exported object from 'namespace:parallel' > sessionInfo() R ve

Re: [Rd] stopping finalizers

2013-02-14 Thread Simon Urbanek
I would argue that addressing this at a generic R level is the wrong place (almost, see below) -- because this is about *specific* finalizers. You don't mind running other people 's finalizers because they don't mess up your connection. Therefore, I'd argue that primarily the approach should be

Re: [Rd] stopping finalizers

2013-02-14 Thread Thomas Lumley
Luke, We're actually adopting the first of your generic approaches. As a more concrete description: There are R objects representing survey data sets, with the data stored in a database table. The subset() method, when applied to these objects, creates a new table indicating which rows of the d

Re: [Rd] stopping finalizers

2013-02-14 Thread Antonio, Fabio Di Narzo
I'm not sure I got your problem right, but you can keep a named copy of your not-to-be-finalized object as long as it needs to be around, so it doesn't go out of scope too early. Something like: local({ dontFinalizeMe <- obj ## ## code which creates copies, overwrites, and indirectly uses

Re: [Rd] stopping finalizers

2013-02-14 Thread luke-tierney
It might help if you could be more specific about what the issue is -- if they are out of scope why does it matter whether the finalizers run? Generically two approaches I can think of: you keep track of whenit is safe to fully run your finalizers and have your finalizers put the objects