yup... for context, the finalizer code calls functions from packages
that are imported by my package.
so, i think (unless something else has gone seriously wrong), those
imported namespaces should still be available prior to my package's
unloading.
(and if imported namespaces are detached prior to
- Original Message -
> From: "Henrik Bengtsson"
> To: "Dan Tenenbaum"
> Cc: "R-devel"
> Sent: Monday, October 27, 2014 12:21:49 PM
> Subject: Re: [Rd] OSX Yosemite (10.10): Are package binaries the same as for
> OSX Mavericks (10.9)?
>
> On Mon, Oct 27, 2014 at 11:23 AM, Dan Tenenbau
On Mon, Oct 27, 2014 at 11:23 AM, Dan Tenenbaum wrote:
>
>
> - Original Message -
>> From: "Dan Tenenbaum"
>> To: "Henrik Bengtsson"
>> Cc: "R-devel"
>> Sent: Monday, October 27, 2014 11:21:59 AM
>> Subject: Re: [Rd] OSX Yosemite (10.10): Are package binaries the same as for
>> OSX Mav
- Original Message -
> From: "Dan Tenenbaum"
> To: "Henrik Bengtsson"
> Cc: "R-devel"
> Sent: Monday, October 27, 2014 11:21:59 AM
> Subject: Re: [Rd] OSX Yosemite (10.10): Are package binaries the same as for
> OSX Mavericks (10.9)?
>
>
>
> - Original Message -
> > From: "
- Original Message -
> From: "Henrik Bengtsson"
> To: "R-devel"
> Sent: Monday, October 27, 2014 11:16:10 AM
> Subject: [Rd] OSX Yosemite (10.10): Are package binaries the same as for OSX
> Mavericks (10.9)?
>
> I'm trying to help someone to troubleshoot possible OSX Yosemite
> issues
I'm trying to help someone to troubleshoot possible OSX Yosemite
issues, but I've only got access to OSX (< 10.9) so I cannot check
myself.
When building/installing binary R packages, there are different
binaries depending on OSX version. For instance, CRAN provides
different binaries for 'OS X S
...and don't forget to make sure all the function that .myFinalizer()
calls are also around. /Henrik
On Mon, Oct 27, 2014 at 10:10 AM, Murat Tasan wrote:
> Eh, after some flailing, I think I solved it.
> I _think_ this pattern should guarantee that the finalizer function is
> still present when n
Eh, after some flailing, I think I solved it.
I _think_ this pattern should guarantee that the finalizer function is
still present when needed:
.STATE_CONTAINER <- new.env(parent = emptyenv())
.STATE_CONTAINER$some_state_variable <- ## some code
.STATE_CONTAINER$some_other_state_variable <- ## som
Hi,
I am trying to create a small extension for R here for embedding the
current time on the R prompt:https://github.com/musically-ut/extPrompt
Things seem to be working overall, but R CMD check . raised a warning:
File '[truncated]..Rcheck/extPrompt/libs/extPrompt.so’: Found non-API call
> to R
