Thank you, but I still think the Writing R Extensions manual needs to be
updated. The manual lists a large number of remapped function names.
These names cannot be used in any package in the current R version
(4.4.1) because R_NO_REMAP is defined in the Debian build script
(intentionally or not
On 6/24/24 09:45, Agner Fog wrote:
On 24/06/2024 08.56, Tomas Kalibera wrote:
In principle it is the NEWS file that gives hints about important
changes and then one can find the details in Writing R Extensions.
The NEWS file as of mid-April says that "R CMD check --as-cran" will
compile C
On 24/06/2024 08.56, Tomas Kalibera wrote:
In principle it is the NEWS file that gives hints about important
changes and then one can find the details in Writing R Extensions.
The NEWS file as of mid-April says that "R CMD check --as-cran" will
compile C++ code with -DR_NO_REMAP. And then in
On 6/24/24 08:25, Agner Fog wrote:
Jarrod Hadfield wrote:
Using Rf_error() rather than error() fixed the problem. Not sure why the
problem was only flagged on Debian, but it
seems to have been triggered by R_NO_REMAP being defined (which will be default
in R 4.5.0).
I had the same problem.
Jarrod Hadfield wrote:
> Using Rf_error() rather than error() fixed the problem. Not sure why the
> problem was only flagged on Debian, but it
> seems to have been triggered by R_NO_REMAP being defined (which will be
> default in R 4.5.0).
I had the same problem. A lot of functions in my packag