OK, actually there is a simple way to achieve this, with minimal
modifications to the Rcpp codebase:
https://github.com/gaborcsardi/Rcpp/commit/8b160547d50d668099dff3802c01001baaf415b6
With this, I can put the functions I want to wrap to a separate file, that
is essentially a header file, with con
On Wed, Feb 12, 2014 at 11:41 AM, Dirk Eddelbuettel wrote:
[...]
> | My question is, is there a way you keep the original sources of the
> wrapped
> | library intact? I would be updating the sources regularly, and I figured
> the
> | best would be not to touch them at all.
>
> Did you see the 'Rc
On 12 February 2014 at 10:57, Gábor Csárdi wrote:
| Hi All, I knew I wouldn't be able avoid Rcpp forever. :)
We're happy to have you now :) I'm sure good things will come of this.
| I am about create R wrappers to a C++ library, old style, not templating. Rcpp
| attributes, and custom as<> and
Hi All, I knew I wouldn't be able avoid Rcpp forever. :)
I am about create R wrappers to a C++ library, old style, not templating.
Rcpp attributes, and custom as<> and wrap() seem to be the way to go, and
they are indeed very appealing. (If only they would have existed when I
started with igraph!)
