[Rcpp-devel] _ZSt4cout warning
JOSHUA.FRENCH at UCDENVER.EDU
Mon Feb 13 19:21:40 CET 2012
Thanks for your response. And thank you (and everyone else) for making
Rcpp/RcppArmadillo/etc. such a great addition to the R community.
Joshua French, Ph.D.
Department of Mathematical and Statistical Sciences
University of Colorado Denver
Joshua.French at ucdenver.edu
Ph: 303-556-6265 Fax: 303-556-8550
On 2/13/12 10:52 AM, "Dirk Eddelbuettel" <edd at debian.org> wrote:
>On 13 February 2012 at 10:32, French, Joshua wrote:
>| I got flagged for the _ZSt4cout warning below on a recent CRAN
>submission of an
>| R package which depends on RcppArmadillo.
>| * checking compiled code ... NOTE
>| Found Œ_ZSt4cout¹, possibly from Œstd::cout¹ (C++)
>| Compiled code should not call functions which might terminate R nor
>| write to stdout/stderr instead of to the console. The detected symbols
>| are linked into the code but might come from libraries and not actually
>| be called.
>| See ŒWriting portable packages¹ in the ŒWriting R Extensions¹ manual.
>| The warning isn't new, but I'd never been flagged on it before. It
>| have been discussed here: http://lists.r-forge.r-project.org/pipermail/
>| I was just wondering if this had been resolved or if work continues to
>Some good news and some bad news:
> Good news: We have this fixed in RcppArmadillo and are ready to upload,
> Conrad also very kindly made a small change at his end.
> Bad news: This depends on a small change in Rcpp, and we ourselves are
> currently being held-up at CRAN on 'R CMD check' output that
> used to pass but no longer does (in this case, using
> and modifying a locked binding which is something Rcpp
>So this should be sorted out "soon" for various values of soon, but we
>been at this for a bit now.
>We will certainly announce new versions here.
>"Outside of a dog, a book is a man's best friend. Inside of a dog, it is
>dark to read." -- Groucho Marx
More information about the Rcpp-devel