This blog is updated daily.
A general description is here.
‘win_iconv’ has been updated: this version has a change in the behaviour with BOMs on UTF-16 and UTF-32 files - it removes BOMs when reading and adds them when writing. (This is consistent with Microsoft applications, but Unix versions of ‘iconv’ usually ignore them.)
Support for repository type ‘win64.binary’ (used for 64-bit Windows binaries for R 2.11.x only) has been removed.
Running R always sets the environment variable ‘R_ARCH’ (as it does on a Unix-alike from the shell-script front-end).
‘system()’ and ‘system2()’ no longer discard output from the command to stdout and stderr as often as they used to.
The 32- and 64-bit distributions have been merged:
There is a combined installer (called ‘R-<version>-win.exe’). When used under 32-bit Windows this works as before and installs 32-bit R. When used under 64-bit Windows there are options to install either or both of 32- and 64-bit R: the default is to install both.
The default package type is ‘"win.binary"’ on both 32- and 64-bit builds: a single repository contains binary packages for both architectures. This is in place for CRAN, CRAN extras and BioC: ‘type = "win64.binary"’ can still be used for any repositories which follow the R 2.11.x convention. With the default filters (see ‘?available.packages’) packages will only be offered if they are available for the current architecture.
The default personal library, e.g. ‘~/R/win-library/2.12’ is now the same for both 32- and 64-bit R.
The recommended 64-bit toolchain has been changed to one that does not add leading underscores. See <URL: http://www.murdoch-sutherland.com/Rtools/> or <URL: http://www.stats.ox.ac.uk/pub/Rtools/>. Any static or import libraries for external software used in installing packages will need to be re-compiled for this toolchain, but the use of DLLs is unaffected.
‘system()’ (and hence ‘shell()’) did not always set the standard file handles properly, so some programs would not run.
‘setWinProgressBar()’ did not check the type of its ‘'title'’ and ‘'label'’ arguments and might have crashed if they were mis-specified. It checks does, thanks to a report by Greg Snow.