btw, Rcpp::rout will need to properly handle the following ostream
member functions:
.flags(), .precision(), .width(), .fill(), .flush(), .unsetf(), .setf()
ie. they can't just be "no-op" functions.
See "include/armadillo_bits/arma_ostream_meat.hpp" as to how these
member functions are used.
2
2011/11/17 Romain François :
>> 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
Le 17/11/11 07:47, c s a écrit :
On Thu, Nov 17, 2011 at 1:54 PM, Dirk Eddelbuettel 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):
On Thu, Nov 17, 2011 at 1:54 PM, Dirk Eddelbuettel 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 th
Hi Conrad,
Thanks so much for proactively posting here! [ And a fresh question below,
please read on. ]
On 17 November 2011 at 13:27, c s wrote:
| Hi everyone,
|
| A beta release (2.3.91) of the updated version of Armadillo is available:
| http://arma.sourceforge.net/download.html
It has been
Hi everyone,
A beta release (2.3.91) of the updated version of Armadillo is available:
http://arma.sourceforge.net/download.html
The following functionality is deprecated in the 2.x series and will
be removed in a future major version (ie. 3.x series):
Support for tying writeable auxiliary (exte
