• using R version 2.14.1 Patched (2012-02-04 r58267)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• using option ‘--install=no’
• checking for file ‘tdm/DESCRIPTION’ ... OK
• this is package ‘tdm’ version ‘2.2.2’
• 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 for executable files ... 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 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 ‘tdm/R/zzz.R’:
  .First.lib calls:
  cat("\n")
  cat("*************************** tdm ***********************************\n")
  cat(" An R Tool for Therapeutic Drug Monitoring \n\n")
  cat(" v 2.2.2 \n\n")
  cat(" TDM is created for your own personal uses and testing purposes. \n")
  cat(" TDM shall be used as a guide or a decision support tool only. \n")
  cat(" Medical decisions should NOT be solely based on the results of \n")
  cat(" this program. Although this program has been tested thoroughly, \n")
  cat(" the accuracy of the information cannot be guaranteed. Once you \n")
  cat(" use tdm, you have automatically agreed with this disclaimer. \n\n")
  cat(" Please type 'run()' to get started. \n")
  cat("*******************************************************************\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 ... OK
• checking Rd contents ... OK
• checking examples ... SKIPPED
• checking PDF version of manual ... OK