• using R version 2.14.2 (2012-02-29)
• using platform: i386-pc-mingw32 (32-bit)
• using session charset: ISO8859-1
• checking for file 'realized/DESCRIPTION' ... OK
• this is package 'realized' version '1.0.1'
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... NOTE
  As from R 2.14.0 all packages need a namespace.
  One will be generated on installation, but it is better to handcraft a
  NAMESPACE file: R CMD build will produce a suitable starting point.
• checking whether package 'realized' can be installed ... OK
• checking installed package size ... NOTE
  installed size is 8.6Mb
  sub-directories of 1Mb or more:
  doc 8.1Mb
• checking package directory ... OK
• checking for portable file names ... 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
• loading checks for arch 'i386'
  ** 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
• loading checks for arch 'x64'
  ** 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 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 'realized/R/realized.R':
  .First.lib calls:
  cat("Realized Library: Realized Variance, Covariance, Correlation Estimation and Tools.\n")
  cat(" R: http://cran.r-project.org\n")
  cat("Copyright (C) 2010 Scott W. Payseur <scott.payseur@gmail.com>\n\n")
  cat("Please report any bugs or feature requests to the author. User's manual\n")
  cat("in the 'realized' library directory.\n\n\n")
  
  Package startup functions should use 'packageStartupMessage' to
  generate messages.
  See section 'Good practice' in ?.onAttach.
  
• 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 'merge.realizedObject':
  'merge.realizedObject'
  
  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 contents of 'data' directory ... OK
• checking data for non-ASCII characters ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking sizes of PDF files under 'inst/doc' ... OK
• checking examples ...
  ** running examples for arch 'i386' ... OK
  ** running examples for arch 'x64' ... OK
• checking PDF version of manual ... OK