Dear R-pkg-dev folk,
The cpp11 package, which was developed yet is no longer maintained by
Jim Hester, now triggers warnings on some CRAN pre-submit checks for
"non-API calls to R" via "SETLENGTH", "SET_TRUELENGTH", and others. The
relevant issue is https://github.com/r-lib/cpp11/issues/355, with
You'll need to fix that note before resubmitting. If you can share a
link to a public repository, people in this list will likely be able to
help.
regards, Mark
On 11/8/23 17:54, Karolina Marek wrote:
Hello,
I have the following case. I would like to resubmit a package to the Cran -
per ARMA,
On 21/08/2023 14:34, Dirk Eddelbuettel wrote:
On 21 August 2023 at 15:16, Ivan Krylov wrote:
| On Mon, 21 Aug 2023 12:02:55 +0100
| Scott Ritchie wrote:
|
| > remotes::install_github("sritchie73/ukbnmr")
| > library(ukbnmr)
| > system.time({ remove_technical_variation(test_data) })
|
| data.ta
On 14/08/2023 14:43, Dirk Eddelbuettel wrote:
On 14 August 2023 at 11:51, Mark Padgham wrote:
| An update of a package of mine got immediately kicked off CRAN because
| an externally-bundled file which had not been changed for years, and
| which included "pragma clang system_heade
An update of a package of mine got immediately kicked off CRAN because
an externally-bundled file which had not been changed for years, and
which included "pragma clang system_header" to suppress warnings. The
concern is fair enough. Removing that nevertheless now generates a heap
of warnings whic
sts only'. I would guess that a relative path
would not work, in general, because the path would be relative to the current
working directory, which of course changes, rather than relative to the path of
the shared object...
Martin Morgan
On 6/19/19, 10:46 AM, "R-package-devel on beh
ystem.file() function?
On June 19, 2019 5:45:51 AM CDT, mark padgham wrote:
Dear All,
I'm developing a package which primarily relies on C code that itself
has to call an external text file representing a dictionary or lookup
table. The location of this file is defined in a C macro, the file
its
Dear All,
I'm developing a package which primarily relies on C code that itself
has to call an external text file representing a dictionary or lookup
table. The location of this file is defined in a C macro, the file
itself packaged in "./inst/dict/" and so currently called as
"#define mylocation
