CRAN Package Check Results for Package pryr

Last updated on 2024-07-01 15:57:36 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.6 64.47 52.06 116.53 NOTE
r-devel-linux-x86_64-debian-gcc 0.1.6 39.33 38.63 77.96 NOTE
r-devel-linux-x86_64-fedora-clang 0.1.6 166.64 NOTE
r-devel-linux-x86_64-fedora-gcc 0.1.6 159.67 NOTE
r-devel-windows-x86_64 0.1.6 48.00 84.00 132.00 NOTE
r-patched-linux-x86_64 0.1.6 49.24 49.70 98.94 OK
r-release-linux-x86_64 0.1.6 51.59 49.13 100.72 OK
r-release-macos-arm64 0.1.6 37.00 OK
r-release-macos-x86_64 0.1.6 52.00 OK
r-release-windows-x86_64 0.1.6 46.00 85.00 131.00 OK
r-oldrel-macos-arm64 0.1.6 41.00 OK
r-oldrel-macos-x86_64 0.1.6 58.00 OK
r-oldrel-windows-x86_64 0.1.6 59.00 98.00 157.00 OK

Check Details

Version: 0.1.6
Check: compiled code
Result: NOTE File ‘pryr/libs/pryr.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘NAMED’, ‘PRCODE’, ‘PRENV’, ‘PRVALUE’, ‘Rf_findVarInFrame3’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. See section ‘Moving into C API compliance’ in the ‘Writing R Extensions’ manual for issues with use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-gcc

Version: 0.1.6
Check: compiled code
Result: NOTE File ‘pryr/libs/pryr.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘NAMED’, ‘PRCODE’, ‘PRENV’, ‘PRVALUE’, ‘Rf_findVarInFrame3’ 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-linux-x86_64-fedora-clang

Version: 0.1.6
Check: compiled code
Result: NOTE File 'pryr/libs/x64/pryr.dll': Found non-API calls to R: 'FRAME', 'HASHTAB', 'NAMED', 'PRCODE', 'PRENV', 'PRVALUE', 'Rf_findVarInFrame3' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual. See section 'Moving into C API compliance' in the 'Writing R Extensions' manual for issues with use of non-API entry points. Flavor: r-devel-windows-x86_64