Closed AndreMikulec closed 6 years ago
I have strong doubts this is related to the day xts was installed. What does it mean to ".Call compile" a package? I have never heard of that before.
It's more likely it is related to the state of your Windows system and R processes using the xts package from your library. You also did not say how you initially installed xts on the release date. Did you install from source, or did you use the binary created by CRAN? Were any other R processes running with the xts shared library loaded at the time you installed the updated version?
I'm closing this because it isn't something I can fix by changing xts source code.
I am saying is the that problem does not seem to exist anymore, except for those people who installed xts with compiling on 2018-07-16. Those people may or may not have the same problem. I am just saying that for those people who do experience that same problem, a simple solution is to just do (today), install.packages('xts") or install.packages("xts", type = "source").
Hello,
If anyone installed xts from CRAN on 2018-07-16 ( the same day as the release date ) and perhaps .Call compiled it, then 'not-good' xts may have been produced with a not working R_RegisterCCallable
However, today (2018-07-22) , when I installed xts in any of the three ways, xts works.
All produced the correct answer.
So, this issue perhaps may be closed.