On 23 Oct 2003, Peter Dalgaard wrote:
Kurt.Hornik@wu-wien.ac.at writes:
Probably, but of a nasty kind which I think we need to get to the bottom of. As I see it there are two possible causes
1. A bug in a Windows library or compiler. Potentially that could affect everything else. 2. A bug in ctest that just happens only to cause visible damage on Windows, but perhaps invisible damage elsewhere.
Either way, I think we need to investigate.
As Brian had written earlier in this thread, we need a reproducible example. If Duncan's example can be reproduced on Windows but not on Linux (and I cannot), odds are in favor of the problem being Windows specific.
No, odds are in favor of the *symptom* being Windows-specific. See above... Problem is, we need a Windows guru to debug in that case.
cor.test.default calls the second arg of prho as as.integer(q + 1), but someone altered the C code (at the last minute before 1.8.0 was frozen) to *double. So I think Peter is probably right.
Brian D. Ripley, ripley@stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595