R 2.13.2 released

[This article was first published on Revolutions, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

The R core team announced today that R 2.13.2 is now available:

The byte pixies have rolled up R-2.13.2.tar.gz at 9:00 this morning. This is intended to be the final release of the 2.13 series, for the benefit of those apprehensive of putting 2.14.x into production use. 

This update fixes a number of minor bugs (for example, pch=”.” will guarantee at least a 1-pixel dot, to support very high-resolution charting), improves performance (date object print much faster now, for example), and adds a few minor features (such as being able to accurately limit memory usage for systems with very large amounts of RAM). The full change log appears after the jump. 

You can download the R 2.13.2 source code now for home builds; binaries for Windows, Mac and Linux will appear on your local CRAN mirror in the next few days. The next release of R, R 2.14.0, is scheduled for October 31.

R-announce mailing list: R 2.13.2 is released



    o mem.limits() now reports values larger than the maximum integer
      (previously documented to be reported as NA), and allows larger
      values to be set, including Inf to remove the limit.

    o The print() methods for classes "Date", "POSIXct" and "POSIXlt"
      respect the option "max.print" and so are much faster for very
      long datetime vectors.  (Suggestion of Yohan Chalabi.)

    o untar2() now works around errors generated with tar files that
      use more than the standard 6 digits for the checksum.

    o install.packages() with Ncpus > 1 guards against simultaneous
      installation of indirect dependencies as well as direct ones.

    o Sweave now knows about a few more Windows' encodings (including
      cp1250 and cp1257) and some inputenx encodings such as koi8-r.

    o postscript(colormodel = "rgb-nogray") no longer sets the sRGB
      colorspace for each colour and so some viewers may render its
      files much faster than the default colormodel ="rgb".

    o The default for pdf(maxRasters=) has been increased from 64 to

    o readBin() now warns if signed = FALSE is used inappropriately
      (rather than being silently ignored).

      It enforces the documented limit of 2^31-1 bytes in a single

    o PCRE has been updated to version 8.13, a bug-fix release with
      updated Unicode tables (version 6.0.0). An additional patch (r611
      from PCRE 8.20-to-be) has been added to fix a collation symbol
      recognition issue.


    o It is possible to build in src/extra/xdr on more platforms.
      (Needed since glibc 2.14 hides its RPC implementation.)

    o configure will find the Sun TI-RPC implementation of xdr (in
      libtirpc) provided its header files are in the search path: see
      the 'R Installation and Administration Manual'.


    o Using a broad exportPattern directive in a NAMESPACE file is no
      longer allowed to export internal objects such as .onLoad and
      .__S3MethodsTable__. .

      These are also excluded from imports, along with .First.lib.


    o fisher.test() had a buglet: If arguments were factors with unused
      levels, levels were dropped and you would get an error saying
      that there should be at least two levels, inconsistently with
      pre-tabulated data.  (Reported by Michael Fay).

    o package.skeleton() will no longer dump S4 objects supplied
      directly rather than in a code file.  These cannot be restored
      correctly from the dumped version.

    o Build-time expressions in help files did not have access to
      functions in the package being built (with R CMD build).

    o Because quote() did not mark its result as being in use,
      modification of the result could in some circumstances modify the
      original call.

    o Plotting pch = '.' now guarantees at least a one-pixel dot if cex
      > 0.

    o The very-rarely-used command-line option --max-vsize was
      incorrectly interpreted as a number of Vcells and not in bytes as
      documented.  (Spotted by Christophe Rhodes.)

    o The HTML generated by Rd2HTML() comes closer to being standards

    o filter(x, recursive = TRUE) gave incorrect results on a series
      containing NAs.  (Spotted by Bill Dunlap.)

    o Profiling stats::mle() fits with a fixed parameter was not

    o retracemem() was still using positional matching.

    o The quantile method for "ecdf" objects now works and is

    o xtabs(~ .., ..., sparse=TRUE) now also works together with an
      exclude = .. specification.

    o decompose() computed an incorrect seasonal component for time
      series with odd frequencies.

    o The pdf() device only includes the definition of the sRGB
      colorspace in the output file for the "rgb" colormodel (and not
      for "gray" nor "cmyk"): this saves ca 9KB in the output file.

    o .hasSlot() wrongly gave FALSE in some cases.

    o Sweave() with keep.source=TRUE could generate spurious NA lines
      when a chunk reference appeared last in a code chunk.

    o \Sexpr[results=rd] in an .Rd file now first tries
      parse_Rd(fragment=FALSE) to allow Rd section-level macros to be

    o The print() method for class "summary.aov" did not pass on
      arguments such as signif.stars when summary() was called on a
      single object.

    o In rare cases ks.test() could return a p-value very slightly less
      than 0 by rounding error.

    o If trunc() was called on a "POSIXlt" vector and the result was
      subsetted, all but the first element was converted to NA.

    o cbind() and rbind() could cause memory corruption when used on a
      combination of raw and logical/integer vectors.

To leave a comment for the author, please follow the link and comment on their blog: Revolutions.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)