[Rcpp-devel] _ZSt4cout warning

| | 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
| | File
| | ?/data/smith/R/packages/incoming/SpatialTools.Rcheck/SpatialTools/libs/
| | SpatialTools.so?:
| |    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 seems to
| | have been discussed here:  http://lists.r-forge.r-project.org/pipermail/
| | rcpp-devel/2011-November/003133.html
| | 
| | I was just wondering if this had been resolved or if work continues to resolve
| | it?
| 
| 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 .Internal
|               and modifying a locked binding which is something Rcpp modules
|               needs).
| 
| So this should be sorted out "soon" for various values of soon, but we have
| been at this for a bit now.  
| 
| We will certainly announce new versions here.

The new RcppArmadillo version is now on CRAN. So packages using RcppArmadillo
should no longer be pestered by the '_ZSt4cout warning' warning.  

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