Brian,
On 25 February 2006 at 10:07, Prof Brian Ripley wrote:
| > I may be misunderstanding you but here it goes: if you are using Rcpp as a
| > means to get to R, you still end up linking with R itself. It is my
| > understanding that this implies the GPL -- or a suitable GPL-compatible
| > lic
On Fri, 24 Feb 2006, Dirk Eddelbuettel wrote:
> On 24 February 2006 at 15:00, Andrew Garbutt wrote:
> | Sorry, that's not quite what I was asking. I was asking more of a "best
> | practice" kind of question. My own C++ codes compile fine and are
> | accessible to R with some great #define magic.
Andrew,
On 24 February 2006 at 15:00, Andrew Garbutt wrote:
| Sorry, that's not quite what I was asking. I was asking more of a "best
| practice" kind of question. My own C++ codes compile fine and are
| accessible to R with some great #define magic. I was noting that the
| Rcpp package has so
t: Friday, February 24, 2006 2:30 PM
> To: Andrew Finley
> Cc: Andrew Garbutt; r-devel@r-project.org
> Subject: Re: [Rd] Rcpp, best method for linking to
>
>
> Hi Andy (and Andy),
>
> I'm not sure why there should be any licensing issues. R itself is
> GPL-ed,
> so
the requirement that the
Rcpp package be installed prior?
Thanks for your time,
Andy
-Original Message-
From: Dominick Samperi [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 2:30 PM
To: Andrew Finley
Cc: Andrew Garbutt; r-devel@r-project.org
Subject: Re: [Rd] Rcpp, best method
Hi Andy (and Andy),
I'm not sure why there should be any licensing issues. R itself is GPL-ed,
so I just followed this convention.
Of course, you can do it yourself with extern "C" and all that. The
purpose of Rcpp.{cpp,hpp} is to enable you to write
readable code (for a C++ programmer) while hi
Hi Andy,
Follow the suggestions for c++ in the Writing R Extensions document.
Wrap your c++ code in extern "C"{}, include your classes in the includes
(e.g., #include "myclass.h") and put the myclass.h and myclass.cpp in
the src directory along with your other code. Then R CMD build ... and R
CMD I
