Hi Fernando and list members,
> For my purposes, I think I could use S4 objects that make C++ copies of
> themselves at creation time, accessible via an external pointer. All
> methods would then make use of the C++ copies for speed, and at the end
> of the session the S4 copies that live in the R
On 6/12/2014 02:08, Dirk Eddelbuettel wrote:
> OS X won't have OpenMP support (yet, apparently some future version
will).
To clarify: This is more of a compiler issue than an OS issue; you can
use OpenMP on OS X with GCC -- for instance:
http://hpc.sourceforge.net/ (verified with standalone C
El jue, 12-06-2014 a las 17:48 +0900, Martin Jakt escribió:
> Hi Fernando and list members,
>
> > For my purposes, I think I could use S4 objects that make C++ copies of
> > themselves at creation time, accessible via an external pointer. All
> > methods would then make use of the C++ copies for s
On 12 June 2014 at 17:48, Martin Jakt wrote:
| Hi Fernando and list members,
|
| > For my purposes, I think I could use S4 objects that make C++ copies of
| > themselves at creation time, accessible via an external pointer. All
| > methods would then make use of the C++ copies for speed, and at t
Hi Dirk,
> | I'm wondering how you've gotten on with this. I'm struggling with a
> | somewhat similar problem in my own package. This uses the 'Rcpp modules'
> | to provide an interface to a couple of C++ functions. This works very
> | well, but accessing the objects (created by new()) after a sav
I forgot to include the mailing list in my previous email.
(Fernando: apologies for the double mailing)
Hi Fernando,
>
> If losing the information is no problem, and you only want to make sure
> your pointers are valid, perhaps you could add a timestamp to them when
> created.
>
> On loading y
