This blog is updated daily..
A general description is here.
‘R CMD check’ now checks for ‘.C()’, ‘.Call()’, ‘.External()’ and
‘.Fortran()’ calls in other packages, and gives a warning on those
found from R itself (which are not part of the API and change without
notice).
‘PACKAGE = ""’ was accepted in ‘.C()’ etc calls, although it was contrary to the documentation. It is now an error.
‘PACKAGE = ""’ was accepted in ‘.C()’ etc calls, although it was
contrary to the documentation. It is now an error.
‘R CMD check’ now checks for ‘.C()’, ‘.Call()’, ‘.External()’ and ‘.Fortran()’ calls in other packages, and gives a warning on those found from R itself (which are not part of the API and change without notice: many will changed for R 2.16.0).
The misuse of ‘.C("name", ..., PACKAGE = foo)’ where ‘foo’ is an arbitrary R object is now an error. (Seen in package ‘coxphf’ and elsewhere.)
The misuse ‘.C"name",(..., PACKAGE = "")’ (see in package ‘RProtoBuf’ is now warned about in ‘R CMD check’, and will be an error in future.
The misuse of ‘.C("name", ..., PACKAGE = foo)’ where ‘foo’ is an
arbitrary R object is now an error. (Seen in package ‘coxphf’ and
elsewhere.)
The code for creating ‘coerce()’ methods could generate false notes about ambiguous selection; the notes have been suppressed for this function.