On 11 April 2012 at 16:13, Whit Armstrong wrote:
| Ok, I see.
|
| My package includes some headers which have direct includes of the
| armadilo headers (hence, they are grabbing the deb testing version of
| Armadillo).
|
| I normally put system headers above R headers, but I think if I
| reverse
Ok, I see.
My package includes some headers which have direct includes of the
armadilo headers (hence, they are grabbing the deb testing version of
Armadillo).
I normally put system headers above R headers, but I think if I
reverse this convention for RcppArmadillo, and let the include guard
kick
On 11 April 2012 at 15:32, Whit Armstrong wrote:
| Thanks, Dirk.
|
| one more quick q.
|
| Should I be doing something to prevent these warnings:
|
|
/usr/local/lib/R/site-library/RcppArmadillo/include/RcppArmadilloConfig.h:64:0:
| warning: "ARMA_DEFAULT_OSTREAM" redefined [enabled by default]
Thanks, Dirk.
one more quick q.
Should I be doing something to prevent these warnings:
/usr/local/lib/R/site-library/RcppArmadillo/include/RcppArmadilloConfig.h:64:0:
warning: "ARMA_DEFAULT_OSTREAM" redefined [enabled by default]
/usr/local/lib/R/site-library/RcppArmadillo/include/armadillo_bits
On 11 April 2012 at 14:16, Whit Armstrong wrote:
| I've been looking in the archives of this list for a while, so forgive
| me if I've missed it.
|
| Does Rcpp expose a version of the DATAPTR macro?
Nothing rings an immediate bell...
| Sadly, I have a need for a void* in my code... So I need a
