CRAN Package Check Results for Package versus

Last updated on 2025-11-22 19:50:46 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.3.1 5.92 65.17 71.09 OK
r-devel-linux-x86_64-debian-gcc 0.3.1 4.40 45.49 49.89 OK
r-devel-linux-x86_64-fedora-clang 0.3.1 32.00 81.78 113.78 OK
r-devel-linux-x86_64-fedora-gcc 0.3.1 12.00 85.51 97.51 OK
r-devel-windows-x86_64 0.3.1 18.00 67.00 85.00 OK
r-patched-linux-x86_64 0.3.1 5.93 58.79 64.72 OK
r-release-linux-x86_64 0.3.0 5.26 54.53 59.79 NOTE
r-release-macos-arm64 0.3.0 4.00 14.00 18.00 NOTE
r-release-macos-x86_64 0.3.1 6.00 59.00 65.00 OK
r-release-windows-x86_64 0.3.0 13.00 78.00 91.00 NOTE
r-oldrel-macos-arm64 0.3.1 1.00 21.00 22.00 OK
r-oldrel-macos-x86_64 0.3.1 10.00 71.00 81.00 OK
r-oldrel-windows-x86_64 0.3.0 12.00 84.00 96.00 OK

Check Details

Version: 0.3.0
Check: compiled code
Result: NOTE File ‘versus/libs/versus.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-release-linux-x86_64, r-release-macos-arm64

Version: 0.3.0
Check: compiled code
Result: NOTE File 'versus/libs/x64/versus.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-release-windows-x86_64