pROC 1.8 is coming with some potential backward-incompatible changes in the namespace
The last significant update of pROC, 1.7, was released a year ago, followed by some minor bug fix updates. In the meantime, the policies of the CRAN repository evolved, and are requiring a significant update of pROC.
Specifically, S3 methods in pROC have always been exported, which means that you could call
roc.formula directly. This is not allowed any longer, and methods must now to be registered as such with
S3method() calls in the
NAMESPACE file. The upcoming version of pROC (1.8) will therefore feature a major cleanup of the namespace.
In practice, this could potentially break some of your code. Specifically, direct call to S3 methods will not work any longer. For instance, the following is incorrect:
rocobj <- roc(...) smooth.roc(rocobj)
Although not documented, it used to work but that will no longer be the case. Instead, you should call the generic function that will dispatch to the proper method:
Other examples include for instance:
# Incorrect: auc.roc(rocobj) # Correct: auc(rocobj) # Incorrect: var.roc(rocobj) # Correct: var(rocobj)
Please make sure you replace any call to a method with the generic. In doubt, consult the Usage section of pROC's manual.
Publié le lundi 23 février 2015 à 23:13 CET
Lien permanent : /blog/2015/02/23/proc-1.8-is-coming-with-some-potential-backward-incompatible-changes-in-the-namespace
Tags : pROC
Commentaires : 0