This blog is updated daily.
A general description is here.
The C code underlying base graphics has been migrated to the ‘graphics’
package (and hence no longer uses ‘.Internal()’ calls).
This may require re-installing some S4-using packages (e.g. ‘timeDate’) which captured the old versions of the R interfaces.
The C code underlying base graphics has been migrated to the ‘graphics’ package (and hence no longer uses ‘.Internal()’ calls).
This may require re-installing some S4-using packages (e.g. ‘timeDate’) which captured the old versions of the R interfaces.
Most of the ‘.Internal()’ calls used in the ‘stats’ package have been migrated to C code in that package.
This means that a number of ‘.Internal()’ calls which have been used by packages no longer exist, including ‘.Internal(cor)’ ‘.Internal(cov)’ and ‘.Internal(update.packages)’.
It also means that packages such as ‘compositions’ which make copies of ‘stats’ functions at installation need to be re-installed.
There is a new function ‘mcaffinity()’ which allows to get or set the CPU affinity mask for the current R process on systems that supports this (currently only Linux was tested successfully). It has no effect on systems that do not support process affinity. Users are not expected to use this function directly (with the exception of fixing libraries that break affinity settings like OpenBLAS) - the function is rather intended to support affinity control in high-level parallel functions. In the future, R may supplement lack of affinity control in the OS by its own bookkeeping via ‘mcaffinity()’ related to processes and threads it spawns.
For ‘R CMD check’, a few people have reported problems with junctions on Windows (although they were tested on Windows 7, XP and Server 2008 machines and it is unknown under what circumstances the problems occur). Setting the environment variable ‘R_WIN_NO_JUNCTIONS’ to a non-empty value (e.g. in ‘~/.R/check.Renviron’) will force copies to be used instead.
C entry points ‘R_GetCurrentSrcref’ and ‘R_GetSrcFilename’ have been added to the API to allow debuggers access to the source references on the stack.
Under some circumstances ‘package.skeleton()’ would give out progress reports that could not be translated and so were displayed by question marks. Now they are always in English. (This was seen for CJK locales on Windows, but may have occurred elsewhere.)