- using R version 2.14.2 RC (2012-02-23 r58468)
- using platform: i686-pc-linux-gnu (32-bit)
- using session charset: UTF-8
- checking for file ‘splus2R/DESCRIPTION’ ... OK
- checking extension type ... Package
- this is package ‘splus2R’ version ‘1.1-0’
- checking package namespace information ... OK
- checking package dependencies ... OK
- checking if this is a source package ... OK
- checking if there is a namespace ... OK
- checking for executable files ... OK
- checking whether package ‘splus2R’ can be installed ... OK
- checking installed package size ... OK
- checking package directory ... OK
- checking for portable file names ... OK
- checking for sufficient/correct file permissions ... OK
- checking DESCRIPTION meta-information ... OK
- checking top-level files ... OK
- checking index information ... OK
- checking package subdirectories ... OK
- checking R files for non-ASCII characters ... OK
- checking R files for syntax errors ... OK
- checking whether the package can be loaded ... OK
- checking whether the package can be loaded with stated dependencies ... OK
- checking whether the package can be unloaded cleanly ... OK
- checking whether the namespace can be loaded with stated dependencies ... OK
- checking whether the namespace can be unloaded cleanly ... OK
- checking for unstated dependencies in R code ... OK
- checking S3 generic/method consistency ... OK
- checking replacement functions ... OK
- checking foreign function calls ... OK
- checking R code for possible problems ... NOTE
File ‘splus2R/R/splus2R_pkg.R’:
.onLoad calls:
require("methods")
Package startup functions should not change the search path.
See section ‘Good practice’ in ?.onAttach.
peaks: warning in embed(rev(as.vector(x)), dim = span): partial
argument match of 'dim' to 'dimension'
rmvnorm: warning in eigen(cov, sym = TRUE): partial argument match of
'sym' to 'symmetric'
signalSeries: warning in numericSequence(from = from, length = len, by
= by): partial argument match of 'length' to 'length.'
- checking Rd files ... OK
- checking Rd metadata ... OK
- checking Rd cross-references ... OK
- checking for missing documentation entries ... OK
- checking for code/documentation mismatches ... OK
- checking Rd \usage sections ... NOTE
S3 methods shown with full name in documentation object 'is.numeric.atomic.vector':
‘is.numeric.atomic.vector’
S3 methods shown with full name in documentation object 'subscript2d':
‘subscript2d.matrix’ ‘subscript2d.data.frame’
The \usage entries for S3 methods should use the \method markup and not
their full name.
See the chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
- checking Rd contents ... OK
- checking for unstated dependencies in examples ... OK
- checking examples ... OK
- checking for unstated dependencies in tests ... OK
- checking tests ... OK
Running ‘showStructure.R’
Comparing ‘showStructure.Rout’ to ‘showStructure.Rout.save’ ...27c27
< @.Data numeric[ length 5] S3 class: factor
---
> $a numeric[ length 5] S3 class: factor
29c29
< @names numeric[ length 5] S3 class: factor
---
> $b numeric[ length 5] S3 class: factor
31c31
< @row.names numeric[ length 5] S3 class: factor
---
> $c numeric[ length 5] S3 class: factor
55c55
< @.Data numeric[ length 5] S3 class: factor
---
> $a numeric[ length 5] S3 class: factor
57c57
< @names numeric[ length 5] S3 class: factor
---
> $b numeric[ length 5] S3 class: factor
59c59
< @row.names numeric[ length 5] S3 class: factor
---
> $c numeric[ length 5] S3 class: factor
Running ‘test1.R’
Running ‘test2.R’
- checking PDF version of manual ... OK