On Thu, Nov 17, 2011 at 1:54 PM, Dirk Eddelbuettel <e...@debian.org> wrote: > Cool, thanks. While I have your attention: the R and the CRAN > infrastructure now also test for use of std::cout in linked-in libraries > (as R has its own i/o buffering; one shall not mix with iostreams): > ... > A quick grep shows that there isn't that much code using it. Would you be up > for defining a new #define (which defaults to TRUE for you but FALSE for > RcppArmadillo) so that we could build without? I'd be happy to prepare a > patch for you. If not, we'll just live with the warning as I'd rather not > constantly patch you code for each new release.
#ifdef'ing the code out would break documented public APIs, so this particular solution is not really doable. Sorry. Furthermore, functions for error notifications (eg. out of bounds access) also print to the cout stream by default. I'm open to looking at solutions which provide a different default stream, as long as it's a C++ std::ostream. _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
