Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Dirk Eddelbuettel
On 30 April 2014 at 10:05, Dirk Eddelbuettel wrote: | | On 30 April 2014 at 10:41, JJ Allaire wrote: | | I think that might be overkill (or something that we can do later if users ask | | for it). | | It is a one-liner, and it just sits there to be used, like OpenMP plugin. | | So in that sen

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Dirk Eddelbuettel
On 30 April 2014 at 10:41, JJ Allaire wrote: | I think that might be overkill (or something that we can do later if users ask | for it). It is a one-liner, and it just sits there to be used, like OpenMP plugin. So in that sense it doesn't hurt, and it may yet help those for which both R < 3.1.0

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Gabor Grothendieck
On Wed, Apr 30, 2014 at 10:40 AM, Dirk Eddelbuettel wrote: > > On 30 April 2014 at 10:15, JJ Allaire wrote: > | I think this PR addresses the issue: > | > | https://github.com/RcppCore/Rcpp/pull/143 > > Very nice. We get the better behaviour of R 3.1.0 when it is available but do > not enforce it.

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Martin Morgan
On 04/30/2014 07:41 AM, JJ Allaire wrote: I think that might be overkill (or something that we can do later if users ask for it). Should I merge the PR? In 3.1 this information is discoverable with "${R_HOME}/bin/R" CMD config CXX1XSTD and friends. On Wed, Apr 30, 2014 at 10:40 AM, Dirk

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread JJ Allaire
I think that might be overkill (or something that we can do later if users ask for it). Should I merge the PR? On Wed, Apr 30, 2014 at 10:40 AM, Dirk Eddelbuettel wrote: > > On 30 April 2014 at 10:15, JJ Allaire wrote: > | I think this PR addresses the issue: > | > | https://github.com/RcppCo

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Dirk Eddelbuettel
On 30 April 2014 at 10:15, JJ Allaire wrote: | I think this PR addresses the issue: | | https://github.com/RcppCore/Rcpp/pull/143 Very nice. We get the better behaviour of R 3.1.0 when it is available but do not enforce it. I may still add a new simple plugin to provide 'c++0x' for users on Win

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Romain Francois
That looks alright to me. But apparently dirk has another way to do it that does not depend on R 3.1.0, whatever works. Romain Le 30 avr. 2014 à 16:15, JJ Allaire a écrit : > Romain, > > I think this PR addresses the issue: > > https://github.com/RcppCore/Rcpp/pull/143 > > I've tested and

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread JJ Allaire
Romain, I think this PR addresses the issue: https://github.com/RcppCore/Rcpp/pull/143 I've tested and it seems to work as intended. Is this fix you were conceiving of or is there something more we should be doing? J.J. On Wed, Apr 30, 2014 at 9:19 AM, Romain Francois wrote: > The plugin as

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Dirk Eddelbuettel
In the very first implementation of the plugin, we actually used -std=c++0x as few people had compilers new enough. Using the environment variable is elegant and pushes the work back to R "which knows" from its configure run. I like that a lot -- but it also makes us depend on R 3.1.0 or later wh

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Gabor Grothendieck
On Wed, Apr 30, 2014 at 9:19 AM, Romain Francois wrote: > The plugin as implemented now is not portable. It would presumably have the same problem on any OS if used witih g++ 4.6.3. An OS-independent way to do this would be to examine the version of g++ used and act accordingly: > sub(".*\\D(\\

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Romain Francois
The plugin as implemented now is not portable. The easiest way to make it portable would be to define the USE_CXX1X environment variable, which R knows how to interpret. This way R would do what makes sense, i.e. use -std=c++0x on windows (for which rtools is limited to gcc 4.6.3 now) and -std

Re: [Rcpp-devel] g++ flags

2014-04-30 Thread Darren Cook
> The problem seems to be that Rcpp uses -std=c++11; however, g++ 4.6.3, > which is what comes with the latest version of Rtools on Windows, uses > -std=c++0x or -std=gnu++0x ... In g++ 4.8.1 those two are deprecated in favour of -std=c++11 and -std=gnu++11 respectively; however they are still ava

[Rcpp-devel] (no subject)

2014-04-30 Thread Gabor Grothendieck
Thr cpp11 plugin as described in this article http://gallery.rcpp.org/articles/first-steps-with-C++11/ gives an error regarding an unknown option when run on Windows with the current version of Rtools (Rtools version 3.1.0.1942) and Rcpp 0.11.1: The problem seems to be that Rcpp uses -std=c+

Re: [Rcpp-devel] Parallel random numbers using Rcpp and OpenMP

2014-04-30 Thread Matteo Fasiolo
Hi Mark, many thanks for all the info, I will certainly have a detailed look at what you are doing. I think it would be nice to have a package that uses C++ level parallelism (OpenMP or not) to speed up random number generation at R level. For example: > library("microbenchmark") > library("mvtn

Re: [Rcpp-devel] Parallel random numbers using Rcpp and OpenMP

2014-04-30 Thread Mark Clements
My two cents worth: For the microsimulation package, we needed uniform random number streams and sub-streams at the C++ level, while supporting R's non-uniform random number distributions[*]. For this, we used the C++ RngStreams library and provided "double *user_unif_rand ()" for user-defined RNG