CRAN Package Check Results for Package plyr

Last updated on 2019-03-27 00:48:09 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.8.4 16.61 64.10 80.71 OK
r-devel-linux-x86_64-debian-gcc 1.8.4 13.03 47.12 60.15 OK
r-devel-linux-x86_64-fedora-clang 1.8.4 100.16 NOTE
r-devel-linux-x86_64-fedora-gcc 1.8.4 92.45 NOTE
r-devel-windows-ix86+x86_64 1.8.4 53.00 120.00 173.00 OK
r-patched-linux-x86_64 1.8.4 15.88 59.68 75.56 OK
r-patched-solaris-x86 1.8.4 119.00 OK
r-release-linux-x86_64 1.8.4 15.36 59.16 74.52 OK
r-release-windows-ix86+x86_64 1.8.4 48.00 118.00 166.00 OK
r-release-osx-x86_64 1.8.4 NOTE
r-oldrel-windows-ix86+x86_64 1.8.4 33.00 150.00 183.00 NOTE
r-oldrel-osx-x86_64 1.8.4 OK

Check Details

Version: 1.8.4
Check: compiled code
Result: NOTE
    File ‘plyr/libs/plyr.so’:
     Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
    
    It is good practice to register native routines and to disable symbol
    search.
    
    See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 1.8.4
Check: Rd \usage sections
Result: NOTE
    S3 methods shown with full name in documentation object 'rbind.fill':
     ‘rbind.fill’
    
    S3 methods shown with full name in documentation object 'rbind.fill.matrix':
     ‘rbind.fill.matrix’
    
    The \usage entries for S3 methods should use the \method markup and not
    their full name.
    See chapter ‘Writing R documentation files’ in the ‘Writing R
    Extensions’ manual.
Flavors: r-release-osx-x86_64, r-oldrel-windows-ix86+x86_64