search for: r_express

...lopment Core Team. > --- >> * Copyright (C) 1998--2004 The R Development Core Team. > 472c472 > < LibExtern char* R_Home; /* Root of the R tree */ > --- >> extern char* R_Home; /* Root of the R tree */ > 499c499 > < extern int R_Expressions INI_as(5000); /* options(expressions) */ > --- >> extern int R_Expressions INI_as(500); /* options(expressions) */ > 514,515c514 > < LibExtern char* R_TempDir INI_as(NULL); /* Name of per-session > dir */ > < extern char R_StdinEnc[31] INI...

...Copyright (C) 1998--2005 The R Development Core Team. --- > * Copyright (C) 1998--2004 The R Development Core Team. 472c472 < LibExtern char* R_Home; /* Root of the R tree */ --- > extern char* R_Home; /* Root of the R tree */ 499c499 < extern int R_Expressions INI_as(5000); /* options(expressions) */ --- > extern int R_Expressions INI_as(500); /* options(expressions) */ 514,515c514 < LibExtern char* R_TempDir INI_as(NULL); /* Name of per-session dir */ < extern char R_StdinEnc[31] INI_as(""); /* Enc...

...eing more than 2500 entries long) seems to imply that the stack size check is somehow skipped. (Perhaps optimized away?) The evaluation depth limit is checked in src/main/eval.c, line 705 [*], followed by stack size check. Can you attach the debugger and take a look at the values of R_EvalDepth and R_Expressions while executing the text? What about R_CStackStart and R_CStackLimit? What is the stack size limit (ulimit -s?) on the machine running this test? -- Best regards, Ivan [*] https://github.com/wch/r-source/blob/8d7ac4699fba640d030703fa010b66bf26054cbd/src/main/eval.c#L705 -------------- next...

Hi all, I'm trying to get the min and max of a sequence of number using a loop like the folllowing. Can anyone point me to why it doesn't work. Thanks. type <- c("min","max") n <- 1:10 for (a in 1:2) { print(type[a](n)) } -- Muhammad

Hi there, I initially asked about this on r-help and was told this might be a better venue. I?m not really convinced from reading the posting guide, but I?ll give it a shot. It was also suggested that the R-Project doesn?t really care about building with ?non-standard? compilers, but I can?t find any evidence of that on the website (indeed, there?s some mention of successful past builds, and the

...f code. It is still somewhat experimental so don't go churning out thousands of lines of GUI code and then blame us for changing the API later on. It does not currently work with GNOME because of event loop differences. See demo(tkttest) and demo(tkdensity). o Internally using global R_Expressions [getOption("expressions")] dramatically speeds up eval.c. o The X11 support code is now in a separate shared library, and flag --gui=none will run R without X11 support (and so x11() and data.entry() will not be available). R BATCH sets --gui=none. o Configuring without...

...f code. It is still somewhat experimental so don't go churning out thousands of lines of GUI code and then blame us for changing the API later on. It does not currently work with GNOME because of event loop differences. See demo(tkttest) and demo(tkdensity). o Internally using global R_Expressions [getOption("expressions")] dramatically speeds up eval.c. o The X11 support code is now in a separate shared library, and flag --gui=none will run R without X11 support (and so x11() and data.entry() will not be available). R BATCH sets --gui=none. o Configuring without...