Re: [R-pkg-devel] Check warning around sprintf: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system

Thanks to all for the inputs and Ivan and Martin for the cleaner code you suggest and which I will definitely use. Iago Sent with Proton Mail secure email. On Monday, 20 November 2023 at 10:09, Martin Maechler wrote: > > > > > > Serguei Sokol > > > > > > on Mon, 20 Nov 2023 10:04:10

Re: [R-pkg-devel] Check warning around sprintf: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system

here n is the maximum number of bytes to write, including the > terminating nul character. For example: > > char msg[8191]; > snprintf(msg, 8191, "criteria: error (%d) -> %s\n", inErr, errStr); > Rf_error(msg); > > or however large you made the error string. > >

[R-pkg-devel] Check warning around sprintf: Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs

Dear all, I am updating a CRAN-archived R package, so it can get back to CRAN. But there is a warning produced in Linux OS that I am not sure to understand and I do not know how to solve, even after looking at ‘Writing portable packages’ in the ‘Writing R Extensions’ manual and after searching

[R-pkg-devel] Tools beyond roxygen2 to write Rd documentation

Dear all, Are there any tools to edit .Rd files by hand (so avoiding roxygen2), as an editor (like could be *RdStudio*, à la RStudio or TeXstudio) or a plugin for ViM or another editor (like could be *vim-Rd*, à la vim-latex)? Thanks for your answers, Stay safe, Iago Sent with