CRAN Package Check Results for Package arrApply

Last updated on 2026-01-08 07:48:45 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.2.1 27.70 25.41 53.11 NOTE
r-devel-linux-x86_64-debian-gcc 2.2.1 18.69 20.94 39.63 NOTE
r-devel-linux-x86_64-fedora-clang 2.2.1 55.00 42.62 97.62 OK
r-devel-linux-x86_64-fedora-gcc 2.2.1 51.00 46.53 97.53 OK
r-devel-windows-x86_64 2.2.1 32.00 60.00 92.00 NOTE
r-patched-linux-x86_64 2.2.1 27.16 23.34 50.50 OK
r-release-linux-x86_64 2.2.1 26.34 23.41 49.75 OK
r-release-macos-arm64 2.2.1 OK
r-release-macos-x86_64 2.2.1 16.00 61.00 77.00 OK
r-release-windows-x86_64 2.2.1 30.00 66.00 96.00 OK
r-oldrel-macos-arm64 2.2.1 OK
r-oldrel-macos-x86_64 2.2.1 17.00 58.00 75.00 OK
r-oldrel-windows-x86_64 2.2.1 37.00 73.00 110.00 OK

Check Details

Version: 2.2.1
Check: compiled code
Result: NOTE File ‘arrApply/libs/arrApply.so’: Found non-API call to R: ‘ATTRIB’ 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: 2.2.1
Check: compiled code
Result: NOTE File 'arrApply/libs/x64/arrApply.dll': Found non-API call to R: 'ATTRIB' 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