[Rcpp-devel] deprecated functionality in Armadillo 2.3.x / 2.4.x and onwards
Romain François
romain at r-enthusiasts.com
Thu Nov 17 08:09:34 CET 2011
Le 17/11/11 07:47, c s a écrit :
> On Thu, Nov 17, 2011 at 1:54 PM, Dirk Eddelbuettel<edd at 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.
That would work for us, as Dirk recently commited a contributed patch to
add Rcpp::rout which is an ostream that forwards to R's console printing
facilities.
Romain
--
Romain Francois
Professional R Enthusiast
http://romainfrancois.blog.free.fr
More information about the Rcpp-devel
mailing list