similar to: Incompatibility between R-2.0.0 and Rggobi_1.0-0.

I have a problem building an extension using ISNAN() on R version 2.0.x. In R 1.9.1 Arith.h and Rmath.h contained code like #ifdef IEEE_754 # define ISNAN(x) (isnan(x)!=0) #else # define ISNAN(x) R_IsNaNorNA(x) #endif #define R_FINITE(x) R_finite(x) int R_IsNaNorNA(double); int R_finite(double); which works. R 2.0.x has # define ISNAN(x) (isnan(x)!=0) unconditionally. This breaks

I have a problem building an extension using ISNAN() on R version 2.0.x. In R 1.9.1 Arith.h and Rmath.h contained code like #ifdef IEEE_754 # define ISNAN(x) (isnan(x)!=0) #else # define ISNAN(x) R_IsNaNorNA(x) #endif #define R_FINITE(x) R_finite(x) int R_IsNaNorNA(double); int R_finite(double); which works. R 2.0.x has # define ISNAN(x) (isnan(x)!=0) unconditionally. This breaks

In the hope of some meaningful response and ignoring the risk of further abuse, let me try to clarify the issue here. I have re-read the 'Writing R Extensions' manual. It seems to me that it clearly says R API functions can be called from from C++ programs, and the API includes the special values ISNAN() and R_FINITE() and the missing test ISNA(). R_FINITE is no problem. It is

Hi, R core developers, I work in the Swiss Institute of Bioinformatics. We have two clusters of Intel Itanium2 clusters for bioinformaticians to crank their data. One piece of software they use heavily is R and BioConductors. I ported the R codes and R packages to this platform already, and am working on optimizing their performance. I'm using Intel C/C++ compiler on this platform running

I have tried compiling R on a dec alpha running digital unix 4.0 and got the following: f77 -shared -o ts.so PPsum.o burg.o eureka.o filter.o pacf.o starma.o stl.o carray.o mburg.o myw.o qr.o -lUfor -lfor -lFutil -lm -lots -lm ld: Warning: Unresolved: R_alloc R_NaReal R_IsNA R_IsNaNorNA R_chk_calloc R_chk_free Rf_error vmaxget vmaxset dqrdc2_ dqrcf_ mkdir ../../../../library/ts/libs gmake[4]:

Dear R developers, I spotted that R_isNA and R_IsNaN could be improved when applied on a vector where we could take out small part of their logic, run it once, and then reuse inside the loop. I setup tiny plain-C experiment. Taking R_IsNA, R_IsNaN from R's arithmetic.c, and building R_vIsNA and R_vIsNaN accordingly. For double input of size 1e9 (having some NA and NaN) I observed following

Hi, FWIW: /* Taken from R/src/main/unique.c */ static int requal(SEXP x, int i, SEXP y, int j) { if (i < 0 || j < 0) return 0; if (!ISNAN(REAL(x)[i]) && !ISNAN(REAL(y)[j])) return (REAL(x)[i] == REAL(y)[j]); else if (R_IsNA(REAL(x)[i]) && R_IsNA(REAL(y)[j])) return 1; else if (R_IsNaN(REAL(x)[i]) && R_IsNaN(REAL(y)[j])) return 1;

Hello R-devel, Best wishes in the new year. I am writing to kindly request new R function so NA_real_ can be more easily detected. Currently if one wants to test for NA_real_ (but not NaN) then extra work has to be done: `is.na(x) & !is.nan(x)` Required functionality is already at C level so to address my request there is not that much to do. Kevin Ushey made a nice summary of current R C api

R-2.9.0/include/R_ext/Arith.h has: int R_IsNA(double); /* True for R's NA only */ int R_IsNaN(double); /* True for special NaN, *not* for NA */ int R_finite(double); /* True if none of NA, NaN, +/-Inf */ #define ISNA(x) R_IsNA(x) /* True for *both* NA and NaN. The first and last lines are contradictory - if R_IsNA is true only for NA, not NaN, then ISNA should be the same.

"nana" is meant to express "NA, really NA". Your suggestion sounds good. On Thu 2 Jan, 2020, 3:38 AM Pages, Herve, <hpages at fredhutch.org> wrote: > Happy New Year everybody! > > The name (is.nana) doesn't make much sense to me. Can you explain it? > > One alternative would be to add an extra argument (e.g. 'strict') to > is.na(). FALSE by

Full_Name: Vilmos Prokaj Version: R 2.7.1 OS: windows Submission from: (NULL) (213.181.195.84) Dear developers, The following line of code (produced by a mistake) caused an infinite loop unique("a",c("a","b")) or also unique(1,1:2) I made a little investigation, and it seems to be that the following function from unique.c is looping infinitely static int

Hi R-devel, I have a question about the differentiation between NA and NaN values as implemented in R. In arithmetic.c, we have int R_IsNA(double x) { if (isnan(x)) { ieee_double y; y.value = x; return (y.word[lw] == 1954); } return 0; } ieee_double is just used for type punning so we can check the final bits and see if they're equal to 1954; if they are, x is NA, if they're

Hi the list, I need to write some efficient distances function, so I read the code for the Euclidean distance. I do not understand the purpose of the line 11 : if x[i] and y[i] are not NA (line 9), can dev be NA ? Christophe #define both_FINITE(a,b) (R_FINITE(a) && R_FINITE(b)) #define both_non_NA(a,b) (!ISNAN(a) && !ISNAN(b)) 1. static double R_euclidean2(double *x, double

On 9/29/19 1:09 PM, Jan Gorecki wrote: > Dear R developers, > > I spotted that R_isNA and R_IsNaN could be improved when applied on a > vector where we could take out small part of their logic, run it once, > and then reuse inside the loop. Dear Jan, Looking at your examples, I just see you have hand-inlined R_IsNA/R_IsNaN, or is there anything more? In principle we could put

Hi, I have an old version of the Rggobi package which now wont load (R 2.0.0). Looking for the package on CRAN does'nt turn up anything and the links on http://www.ggobi.org/RSggobi.html don't work. Does anybody know where I can get the latest version of RSggobi or Rggobi? Thanks, ------------------------------------------------------------------- Rajarshi Guha <rxg218 at

Hi R users. I am experimenting with ubuntu 7.04 Feisty. I install the ggobi package with apt-get. I got almost all the packages, but when I try to obtain rggobi, I got this message: ------------------------------------------------------------------------------------------------- install.packages("rggobi") Aviso en install.packages("rggobi") : argument 'lib' is

Happy New Year everybody! The name (is.nana) doesn't make much sense to me. Can you explain it? One alternative would be to add an extra argument (e.g. 'strict') to is.na(). FALSE by default, and ignored (with or w/o a warning) when the type of 'x' is not "numeric". H. On 12/31/19 22:16, Jan Gorecki wrote: > Hello R-devel, > > Best wishes in the new

I am currently using R 2.15.0 with R Tools 2.15 (in Windows XP). I downloaded the source for RGgobi and extracted it to a folder.   Then I tried compiling and installing with the following command and got an error message: -------------------------------------------------------------------------------------------- D:\Work\tmp>R CMD INSTALL --build "D:\\DPF\\Rggobi\\rggobi" *

I am currently using R 2.15.0 with R Tools 2.15 (in Windows XP). I downloaded the source for RGgobi and extracted it to a folder.   Then I tried compiling and installing with the following command and got an error message: ------------------------------------------------------------------------------------------------------------------ D:\Work\tmp>R CMD INSTALL --build

I am trying to install R-0.63.3 on a Digital Alpha running OSF V4.0D, and having some difficulties. Can anyone help? Also, I found some "oddities" in the installation process. I expect that this message is read by the developers, maybe some of my suggestions can be incorporated into future releases. Please reply to me directly (as well as possibly also to this mailing list): I am not a