Thanks for the prompt reply, and the slick package. Indeed, it appears to be
unnecessary. I must have created it in an attempt to fix another problem and
lost track of that.
--
Sent from my phone. Please excuse my brevity.
On March 3, 2018 9:52:57 AM PST, Dirk Eddelbuettel wrote:
>
>On 3 Mar
Thanks very much, Dirk. I've got things working now, thanks to your help.
Part of my problem was slurring together @export and [[Rcpp::export]].
I really appreciate the help.
Dan.
> On Mar 3, 2018, at 12:25 PM, Dirk Eddelbuettel wrote:
>
>
> On 3 March 2018 at 15:57, Daniel Kelley wrote:
On 3 March 2018 at 09:32, Jeff Newmiller wrote:
| I have an existing legacy.c file with legacy.h interface that I am putting
into a package. I figured out how to create an rcpp glue file that uses an
extern "C" block to include the .h file so my C++ function can call it.
|
| However, it looks l
I have an existing legacy.c file with legacy.h interface that I am putting into
a package. I figured out how to create an rcpp glue file that uses an extern
"C" block to include the .h file so my C++ function can call it.
However, it looks like Rcpp is defining the OBJECTS variable before I put
On 3 March 2018 at 15:57, Daniel Kelley wrote:
| Short version: are there any docs on namespace difficulties that might be
| encountered whilst adding C++ to an R project that already uses C?
In short, yes.
It has to do with the symbol autogeneration _and registration_ we support
since last year
Short version: are there any docs on namespace difficulties that might be
encountered whilst adding C++ to an R project that already uses C?
Long version (and I really do apologize for the length).
I am trying to convert some of the C in my biggish package ("oce", 70 kloc R
and 7 kloc C) from C t
