I've forgotten to submit this as bug report
(and haven't easily seen how to debug).
The bug is both for is.na() and is.nan() {which makes much sense since
the C code of the two is very similar!};
only one is shown below.
Martin
------- start of forwarded message -------
From: Martin Maechler <maechler@stat.math.ethz.ch>
To: R-core@stat.math.ethz.ch
Subject: another is.nan BUG found by gctorture-testing demo(is.things)
Date: Thu, 12 Apr 2001 14:51:06 +0200
demo() being part of strict tests (since this morning),
reveals another bug in is.nan()
in both branches, but already in 1.2.2
(ie. certainly not caused by Peter's recent fix) :
gctorture(FALSE) # default
is.nan(NULL)
#-> logical(0)
gctorture()
is.nan(NULL)
Looks pretty strange : {calling it subsequently does sometimes not reproduce}
------- end of forwarded message -------
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !) To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._