Last updated on 2024-12-18 19:49:34 CET.
| Package | NOTE | OK |
|---|---|---|
| grr | 10 | 3 |
Current CRAN status: NOTE: 10, OK: 3
Version: 0.9.5
Check: Rd files
Result: NOTE
checkRd: (-1) matches.Rd:33: Lost braces; missing escapes or markup?
33 | be set to an index value of \code{length+1}. If {indexes=FALSE}, they will
| ^
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64
Version: 0.9.5
Check: compiled code
Result: NOTE
File ‘grr/libs/grr.so’:
Found non-API call to R: ‘STRING_PTR’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc
Version: 0.9.5
Check: compiled code
Result: NOTE
File ‘grr/libs/grr.so’:
Found non-API call to R: ‘STRING_PTR’
File ‘grr/libs/grr.so’:
Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc
Version: 0.9.5
Check: compiled code
Result: NOTE
File 'grr/libs/x64/grr.dll':
Found non-API call to R: 'STRING_PTR'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
Flavor: r-devel-windows-x86_64