search for: parsestatus

Hi, The behavior of ``` SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); ``` defined in `src/include/R_ext/Parse.h` appears to be inconsistent depending on the string to be parsed. Trying to parse a string such as `"list(''=1+"` sets the `ParseStatus` to incomplete parsing error but trying to parse `"list(''=123"` will resu...

In src/main/gram.y, the documentation for R_ParseVector has a wrong signature: SEXP R_ParseVector(TextBuffer *text, int n, ParseStatus *status) should be SEXP R_ParseVector(SEXP text, int n, ParseStatus *status) In addition, the two occurrences of "IOBuffer" in the documentation should be replaced by "IoBuffer". version.string = Version 2.3.0 beta (2006-04-14 r37779) Best, Hsiu-Khuern Tang HP Labs

...nd LaTeX parsers in tools. > */ > > ``` > > Could this be related to be issue ? > > Le sam. 30 nov. 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a > ?crit : > >> Hi, >> >> The behavior of >> ``` >> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); >> ``` >> defined in `src/include/R_ext/Parse.h` appears to be inconsistent >> depending on the string to be parsed. >> >> Trying to parse a string such as `"list(''=1+"` sets the >> `ParseStatus` to incomplete parsing error but trying...

Dear List, When I try to parse code containing newline characters with R_ParseVector, I get a compilation error. How can I compile code that includes comments and newlines? I am using the following: void* my_compile(char *code) { SEXP cmdSexp, cmdExpr = R_NilValue; ParseStatus status; PROTECT (cmdSexp = allocVector (STRSXP, 1)); SET_STRING_ELT (cmdSexp, 0, mkChar (code)); PROTECT (cmdExpr = R_ParseVector (cmdSexp,-1,&status, R_NilValue)); UNPROTECT_PTR (cmdSexp); if (status != PARSE_OK) { return (void*)0; } else { ret...

...to be issue ? > >> > >> Le sam. 30 nov. 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a > >> ?crit : > >> > >>> Hi, > >>> > >>> The behavior of > >>> ``` > >>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); > >>> ``` > >>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent > >>> depending on the string to be parsed. > >>> > >>> Trying to parse a string such as `"list(''=1+"` sets the > >>&gt...

..."R_HOME=/apps/R/install/lib64/R"); const char *R_argv[]= {"RInterfaceTest", "--gui=none", "--no-save", "--no-readline", "--silent"}; Rf_initialize_R(sizeof(R_argv)/sizeof(R_argv[0]), const_cast<char **>(R_argv)); setup_Rmainloop(); ParseStatus status; SEXP cmdSexp, cmdexpr = R_NilValue; int error; string rcommand = "f<-file(paste(tempdir(), \"/Routput.txt\", sep = \"\"), open=\"wt+\")\nsink(f)\n"; PROTECT(cmdSexp = allocVector(STRSXP, 1)); SET_STRING_ELT(cmdSexp, 0, mkChar(rcommand.c_str())); c...

...: bad value Fatal error: unable to initialize the JIT That aside, here is the code with newlines that fails to parse. I hope it will paste alright here. #include "embeddedRCall.h" #include <R_ext/Parse.h> int main(int argc, char *argv[]) { SEXP e, tmp; int hadError; ParseStatus status; init_R(argc, argv); PROTECT(tmp = mkString("\n\r ls()")); PROTECT(e = R_ParseVector(tmp, 1, &status, R_NilValue)); if (status != PARSE_OK) { printf("boo boo\n"); } else { PrintValue(e); R_tryEval(VECTOR_ELT(e,...

...ed parser here). The same problem exists at least in the Rd and LaTeX parsers in tools. */ ``` Could this be related to be issue ? Le sam. 30 nov. 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a ?crit : > Hi, > > The behavior of > ``` > SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); > ``` > defined in `src/include/R_ext/Parse.h` appears to be inconsistent > depending on the string to be parsed. > > Trying to parse a string such as `"list(''=1+"` sets the > `ParseStatus` to incomplete parsing error but trying to parse > `"li...

...R internal functions. What I read is just lots of macro names defined in the Rinternals.h or Rdefines like R_Parse, Rf_install and so on. But where can I get the detailed information about the parameters of these macro? For example, what about the parameters of SEXP R_ParseVector(SEXP, int, ParseStatus *)? Thank you very much! Baiyi Song Computer Engineering Institute Dortmund Univercity

...sion 2.6.0 Under development (unstable) (2007-04-06 r41080) $ export LD_LIBRARY_PATH=`${RPROG} RHOME`/lib $ cat parseEvalS4.c #include <Rinternals.h> #include <Rembedded.h> #include <R_ext/Parse.h> int main(int argc, char *argv[]) { SEXP e, val; int i, errorOccurred; ParseStatus status; char *cmds[] = { "show(5)", "show(cbind2)", "cbind2" }; argv[0] = "R"; Rf_initEmbeddedR(argc, argv); for (i = 0; i < 3; i++) { printf("** I **: Executing command: %s\n", cmds[i]); PROTECT(e = R_ParseVecto...

...``` >> >> Could this be related to be issue ? >> >> Le sam. 30 nov. 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a >> ?crit : >> >>> Hi, >>> >>> The behavior of >>> ``` >>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); >>> ``` >>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent >>> depending on the string to be parsed. >>> >>> Trying to parse a string such as `"list(''=1+"` sets the >>> `ParseStatus` to incomplete...

...I am using the following code snippet for initializing R, parsing and evaluation of R expression // For initialization int res= Rf_initEmbeddedR(R_argc, (char**)R_argv); // For parsing and evaluation SEXP cmd1= Rf_mkChar(rscript); SEXP cmdSexp, cmdexpr, sresult = R_NilValue; ParseStatus status; R_len_t i=0; PROTECT(cmdSexp = Rf_allocVector(STRSXP, 1)); SET_STRING_ELT(cmdSexp, 0, cmd1); // parsing vector for R expressions cmdexpr = PROTECT(R_ParseVector(cmdSexp, -1, &status, R_NilValue)); if (status != PARSE_OK) { UNPROTECT(2); // error handling return; } for(i...

...de, system info and error information list behand ----------------------------- 1, my example code lists here: ----------------------------- #include .... void *ts_thread(){ SEXP e, tmp; int hadError; int argc = 0; char *argv[1]; ParseStatus status; init_R(argc, argv); PROTECT(tmp = mkString("{print(lh)}")); PROTECT(e = R_ParseVector(tmp, 1, &status, R_NilValue)); PrintValue(e); R_tryEval(VECTOR_ELT(e,0), R_GlobalEnv, &hadError); UNPROTECT(2); end_R(); }...

.... 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a >>> >> ?crit : >>> >> >>> >>> Hi, >>> >>> >>> >>> The behavior of >>> >>> ``` >>> >>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); >>> >>> ``` >>> >>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent >>> >>> depending on the string to be parsed. >>> >>> >>> >>> Trying to parse a string such as `"list('&...

...e sections from R_ReplDLLdo1() and friends, which could then be simplified to use this function, internally. Regards Thomas Friedrichsmeier -------------- next part -------------- /* print mode: 0: print if visible. 1: always print 2: never print */ SEXP R_DLLGenericEplDo1 (unsigned char *buffer, ParseStatus *parse_status, Rboolean set_last_sym_value, int print_mode, Rboolean do_toplevel_callbacks) { int c; ParseStatus status; SEXP value; SEXP rho = R_GlobalEnv; Rboolean wasDisplayed = FALSE; while((c = *buffer++)) { R_IoBufferPutc(c, &R_ConsoleIob); if(c == ';' |...

...> >> Le sam. 30 nov. 2019 ? 14:04, Laurent Gautier <lgautier at gmail.com> a >> >> ?crit : >> >> >> >>> Hi, >> >>> >> >>> The behavior of >> >>> ``` >> >>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); >> >>> ``` >> >>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent >> >>> depending on the string to be parsed. >> >>> >> >>> Trying to parse a string such as `"list(''=1+"` sets...

Dear all, my aim is to integrate R in an interactive visualisation software called Bulk Analyzer developed by VrVis (http://www.vrvis.at). the code: SEXP e, tmp; ParseStatus status; PROTECT(tmp = mkString("x <- c(1.234,-3.45)")); PrintValue(tmp); PROTECT(e = R_ParseVector(tmp, -1, &status, R_NilValue)); PrintValue(e); UNPROTECT(2); produces the following output: [1] "x <- c(1.234,-3.45)" expression(x <- c(1, -3)) I'm using MS...

...urent Gautier > <lgautier at gmail.com <mailto:lgautier at gmail.com>> a > >> ?crit : > >> > >>> Hi, > >>> > >>> The behavior of > >>> ``` > >>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); > >>> ``` > >>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent > >>> depending on the string to be parsed. > >>> > >>> Trying to parse a string such as `"list(''=1+"` sets...

...UNPROTECT(1); } void r_trigger_callback2() { int errorOccurred; SEXP f = NULL; f = allocVector(LANGSXP, 1); SETCAR(f, callback2); PROTECT(f); R_tryEval(f, R_GlobalEnv, &errorOccurred); UNPROTECT(1); } void r_exec(char *code) { SEXP cmdSexp, cmdExpr = R_NilValue; ParseStatus status; int i,errorOccurred; SEXP e; PROTECT (cmdSexp = allocVector (STRSXP, 1)); SET_STRING_ELT (cmdSexp, 0, mkChar (code)); PROTECT (cmdExpr = R_ParseVector (cmdSexp,-1,&status,R_NilValue)); UNPROTECT_PTR (cmdSexp); if (status == PARSE_OK) { for (i = 0; i < l...

...> a > >>>>>> ?crit : > >>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>> The behavior of > >>>>>>> ``` > >>>>>>> SEXP R_ParseVector(SEXP, int, ParseStatus *, SEXP); > >>>>>>> ``` > >>>>>>> defined in `src/include/R_ext/Parse.h` appears to be inconsistent > >>>>>>> depending on the string to be parsed. > >>>>>>> > >>>>>>> Trying to p...