• For ‘tiff(type = "windows")’, the numbering of per-page files except the last was off by one.

• Loading package ‘stats’ (which is done for a default session) would switch line endings on ‘stdout’ and ‘stdout’ from CRLF to LF. This affected ‘Rterm’ and ‘R CMD BATCH’.

• The compatibility function ‘x11()’ had not kept up with changes to ‘windows()’, and issued warnings about bad parameters. (PR#14880)

• The ‘Sys.glob()’ function didn't handle UNC paths as it was designed to try to do. (PR#14884)

• There are two new environment variables which control the defaults for command-line options.

  If ‘R_WIN_INTERNET2’ is set to a non-empty value, it is as if ‘--internet2’ was used.

  If ‘R_MAX_MEM_SIZE’ is set, it gives the default memory limit if ‘--max-mem-size’ is not specified: invalid values being ignored.

• There are two new environment variables which control the defaults for command-line options.

  If ‘R_WIN_INTERNET2’ is set to a non-empty value, it is as if ‘--internet2’ was used.

  If ‘R_MAX_MEM_SIZE’ is set, it gives the default memory limit if ‘--max-mem-size’ is not specified: invalid values being ignored.

• For ‘tiff(type = "windows")’, the numbering of per-page files except the last was off by one.

• The ‘Sys.glob()’ function didn't handle UNC paths as it was designed to try to do. (PR#14884)

• The ‘Sys.glob()’ function didn't handle UNC paths as it was designed to do. (PR#14884)

• The compatibility function ‘x11()’ had not kept up with changes to ‘windows()’, and issued warnings about bad parameters. (PR#14880)

• Loading package ‘stats’ (which is done for a default session) would switch line endings on ‘stdout’ and ‘stdout’ from CRLF to LF. This affected ‘Rterm’ and ‘R CMD BATCH’.

• For ‘tiff(type = "windows")’, the labelling of per-page graphs except the last was off by one.

• Due to a race condition, some graphics changes were not flushed to the display if another graphics window was closed at nearly the same time. (Reported by Michael Sumner.)

• The behaviour of ‘unlink()’ for reparse points (including junctions and symbolic links) has changed. It no longer follow links (deleting the contents of the link target rather than the link), and it is able to delete the link itself (given sufficient permissions).

2.15.0 INSTALLER (Windows)

• The installer has many fewer options with more files always being installed, as a few Mb of file space is nowadays no longer an issue.

2.15.0 PACKAGE INSTALLATION (Windows)

• ‘Rcmd INSTALL --merge-multiarch’ will work (but do a normal install) if only one architecture is installed.

• As the current toolchain uses only 32-bit executables, it is possible to compile a package for both architectures on 32-bit Windows provided both architectures of R have been installed: use ‘Rcmd INSTALL --compile-both’.

• The 32-bit and 64-bit builds are now treated equally, as it is anticipated that 64-bit R will soon be (if not already) the more commonly used. This entails:

  The ‘Rterm’ or ‘Rgui’ title mentions 32-bit as well as 64-bit.

  The desktop icons are labelled ‘R i386’ and ‘R x64’.

  ‘R CMD INSTALL’ for a package with compiled code will fail if compilation fails for any of the installed sub-architectures: use ‘--no-multiarch’ to override this.

• ‘postscript(file = "|cmd")’ now works on Windows.

• ‘file.symlink()’ is now implemented on NTFS file systems on Vista or later, for accounts which have suitable permissions (and most will not). It can link existing directories, and existing-or-not files.

• The behaviour of ‘unlink()’ for reparse points (including junctions and symbolic links) has changed. It no longer follow links (deleting the contents of the link target rather than the link), and it is able to delete the link itself (given sufficient permissions).

• There is a new function ‘Sys.junction()’ to create junction points on NTFS file systems.

• C-level error formats now use the trio library, and so for example use ‘1.53e-11’ (as required by C99) rather than ‘1.53e-011’.

CHANGES IN R 2.15.0 INSTALLER (Windows)

• The installer has many fewer options with more files always being installed, as file space is nowadays no longer an issue.

• It is now possible to select ‘64-bit Files’ from the standard installer even on a 32-bit version of Windows.

CHANGES IN R 2.15.0 PACKAGE INSTALLATION (Windows)

• As the current toolchain uses only 32-bit executables, it is possible to compile a package for both architectures on 32-bit Windows provided both architectures of R have been installed: use ‘R CMD INSTALL --compile-both’.

2.15.0 NEW FEATURES (Windows)

• The 32-bit and 64-bit builds are now treated equally, as it is anticipated that 64-bit R will soon be (if not already) the more commonly used. This entails:

  The ‘Rterm’ or ‘Rgui’ title mentions 32-bit as well as 64-bit.

  The desktop icons are labelled ‘R i386’ and ‘R x64’.

  ‘R CMD INSTALL’ for a package with compiled code will fail if compilation fails for any of the installed sub-architectures: use ‘--no-multiarch’ to override this.

• ‘postscript(file = "|cmd")’ now works on Windows.

• ‘file.symlink()’ is now implemented on NTFS file systems on Vista or later, for accounts which have suitable permissions (and most will not). It can link existing directories, and existing-or-not files.

• The behaviour of ‘unlink()’ for reparse points (including junctions and symbolic links) has changed. It no longer follow links (deleting the contents of the link target rather than the link), and it is able to delete the link itself (given sufficient permissions).

• There is a new function ‘Sys.junction()’ to create junction points on NTFS file systems.

• C-level error formats now use the trio library, and so for example output ‘1.53e-11’ (as required by C99) rather than ‘1.53e-011’.

2.15.0 INSTALLER (Windows)

• The installer has many fewer options with more files always being installed, as file space is nowadays no longer an issue.

• It is now possible to select ‘64-bit Files’ from the standard installer even on a 32-bit version of Windows.

2.15.0 PACKAGE INSTALLATION (Windows)

• As the current toolchain uses only 32-bit executables, it is possible to compile a package for both architectures on 32-bit Windows provided both architectures of R have been installed: use ‘R CMD INSTALL --compile-both’.

• The 32-bit and 64-bit builds are now treated equally, as it is anticipated that 64-bit R will soon be (if not already) the more commonly used. This entails:

  The ‘Rterm’ or ‘Rgui’ title mentions 32-bit as well as 64-bit.

  The desktop icons are labelled ‘R i386’ and ‘R x64’.

  ‘R CMD INSTALL’ for a package with compiled code will fail if compilation fails for any of the installed sub-architectures: use ‘--no-multiarch’ to override this.

• ‘postscript(file = "|cmd")’ now works on Windows.

• ‘file.symlink()’ is now implemented on NTFS file systems on Vista or later, for accounts which have suitable permissions (and most will not). It can link existing directories, and existing-or-not files.

• The behaviour of ‘unlink()’ for reparse points (including junctions and symbolic links) has changed. It no longer follow links (deleting the contents of the link target rather than the link), and it is able to delete the link itself (given sufficient permissions).

• There is a new function ‘Sys.junction()’ to create junction points on NTFS file systems.

• C-level error formats now use the trio library, and so for example use ‘1.53e-11’ (as required by C99) rather than ‘1.53e-011’.

CHANGES IN R 2.15.0 INSTALLER (Windows)

• The installer has many fewer options with more files always being installed, as file space is nowadays no longer an issue.

• It is now possible to select ‘64-bit Files’ from the standard installer even on a 32-bit version of Windows.

CHANGES IN R 2.15.0 PACKAGE INSTALLATION (Windows)

• As the current toolchain uses only 32-bit executables, it is possible to compile a package for both architectures on 32-bit Windows provided both architectures of R have been installed: use ‘R CMD INSTALL --compile-both’.