Hi Richard. On 2 March 2012 at 10:32, Richard Chandler wrote: | Hi Dirk, | | Thanks for those suggestions. I am trying them both but without | success so far. I will keep at it, but first, I wonder how serious | these warnings are? I can still pass R CMD check, and my program seems
You never showed them to us, so we can't tell. | to work very well. Could something disastrous happen if I ignore the | warnings? Do you think CRAN would accept the package? For CRAN you probably want a package framework anyway rather than an inline call. And what R CMD check says matters -- which is a superset of compiler warnings plus a boatload or two of other tests. Which are sometimes a pain, but beneficial to all of us in the long run. Dirk | Richard | | On Thu, Mar 1, 2012 at 5:35 PM, Dirk Eddelbuettel <[email protected]> wrote: | > | > Richard, | > | > On 1 March 2012 at 15:36, Dirk Eddelbuettel wrote: | > | | > | Hi Richard, | > | | > | On 1 March 2012 at 16:25, Richard Chandler wrote: | > | | Hi, | > | | | > | | I am trying to call Rdqags (from R_ext/Applic.h) in a C++ program that | > | | uses RcppArmadillo. Everything seems to work fine except the compiler | > | | warns about conflicts. Is there a way to avoid these conflicts? Could | > | | they cause any unforeseen problems? Below is a self-contained example | > | | illustrating the problem. Note that RcppArmadillo is not actually | > | | required in the example, but it is in my program. See below for | > | | sessionInfo(). | > | > Another idea would be to dig up some old posts on the about how Rcpp lets you | > get R API access points directly. Davor used that to get to loess. That way | > you would get to use Rdqags but without needing the conflicting header. Just | > another thought. | > | > Dirk | > | > -- | > "Outside of a dog, a book is a man's best friend. Inside of a dog, it is too | > dark to read." -- Groucho Marx -- "Outside of a dog, a book is a man's best friend. Inside of a dog, it is too dark to read." -- Groucho Marx _______________________________________________ Rcpp-devel mailing list [email protected] https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
