Thanks Dirk and Uwe! Mostly thinking out loud, I wonder how open cran would
be to something where if C++17 is not available from the compiler a package
could
1. Have checks in the R code before the call to throw before the function
is called
2. Using macros so that if c++17 is not available you cr
On 31.07.2021 04:15, Tim Keitt wrote:
Kind of figured that out looking around on github. I added a config
(borrowed from one of your repos) to test for CXX17. I'm not sure its quite
working for me yet but I will figure it out. A couple of questions:
1) I had C++17 in the system requirements i
Kind of figured that out looking around on github. I added a config
(borrowed from one of your repos) to test for CXX17. I'm not sure its quite
working for me yet but I will figure it out. A couple of questions:
1) I had C++17 in the system requirements in the description file but might
remove it
Section 2.7.3 'C++ Support' of the R Admin manual says, "C++ is not used by R
itself, but support is provided ...". This is all stored from when R itself
is configure (prior to compiling) and override-able in package configuration
(Section 2.7.3 covers that) but as that in other places _it all d
Hi Tim, if you look in the history of the mailing list there's been a few
questions surrounding c++17. But most of what I've seen is to have flags to
turn on and off the c++17 parts of your code. I get it, and not impossible
to do cleanly with boost macros, but kind of a bummer. It would be nice t
