<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
A user of my CRAN package (pROC) reported getting the following
error:<br>
<br>
<blockquote type="cite">
<p class="MsoNormal"><span style="font-family:"Courier
New"">Error in delongPlacementsCpp(roc) :
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Courier
New""> function 'enterRNGScope' not provided by package
'Rcpp'<o:p></o:p></span></p>
</blockquote>
(<span style="font-family:"Courier New"">delongPlacementsCpp
</span>is a function of my package that does *not* use the runif
sugar.)<br>
<br>
He was using a slightly older version of Rcpp (0.10.6), and it seems
that upgrading to 0.11.1 fixed the problem.<br>
However, this function works perfectly fine with Rcpp 0.10.6...<br>
Apparently (and I was able to reproduce this), the reason he got
this error is because he had installed a binary version (he is in a
Windows environment) of my package that was compiled with Rcpp
0.11.*. As he already had a compatible version Rcpp installed
(0.10.6), it didn't get updated. And he ended up having a version
mismatch... <br>
<br>
So my question is: how can I avoid this problem in the future? <br>
<br>
Right now I'm going to push an update that will require Rcpp 0.11.1,
but it doesn't feel quite right... 0.10.6 is working perfectly fine
after all! And what happens when Rcpp 0.12.0 is released? Do I need
to push an update again just in case?<br>
Is there any way to enforce that the installed version of Rcpp
matches the version that was present at compile time? Or more
generally, what is the recommended way to deal with this?<br>
<br>
Best wishes,<br>
Xavier<br>
<br>
<br>
</body>
</html>