Displaying 6 results from an estimated 6 matches for "r_parse1".
2005 Oct 03
2
access to R parse tree for Lisp-style macros?
...quot;))
expression(1 + 2)
what I see looks exactly like R code - that '1 + 2' expression doesn't
look very "parsed" to me. Is that really it, or is there some sort of
Scheme-like parse tree hiding underneath? I see that the interactive
Read-Eval-Print loop basically calls R_Parse1() in "src/main/gram.c",
but from there I'm pretty much lost.
Also, what happens at package build time? I know that R CMD INSTALL
generates binary *.rdb and *.rdx files for my package, but what do
those do exactly, and how do they relate to the REPL and R_Parse1()?
Finally, are ther...
2003 Apr 16
0
vignette segfault bt
...bolValue (c=255)
at /ext/R/cvs/R-devel/src/main/gram.y:1673
#4 0x080aab01 in token () at /ext/R/cvs/R-devel/src/main/gram.y:1744
#5 0x080aaefa in Rf_yylex () at /ext/R/cvs/R-devel/src/main/gram.y:1886
#6 0x080a87e4 in Rf_yyparse () at
/usr/local/share/bison/bison.simple:595
#7 0x080a98cd in R_Parse1 (status=0x46)
at /ext/R/cvs/R-devel/src/main/gram.y:948
#8 0x080a9bee in R_Parse (n=-1, status=0xbfffcd68)
at /ext/R/cvs/R-devel/src/main/gram.y:1083
#9 0x081175d1 in do_parse (call=0x883d674, op=0x8205024,
args=0x8839138,
env=0x9207e84) at source.c:76
#10 0x080c99e4 in do_internal (c...
2004 Jun 25
4
Bug in parse(text = <long polynom>) (PR#7022)
Merci beaucoup, Jean,
for the bug report -- which I'm no "completeing" to R-bugs
>>>>> "Jean" == Jean Coursol <coursol@cristal.math.u-psud.fr>
>>>>> on Thu, 24 Jun 2004 15:22:37 +0200 (CEST) writes:
Jean> I was exploring the polynom library with students:
<and found a segmentation fault from parsing a long expression>
2003 Apr 05
0
sweave/gc segfault bt
...in SymbolValue (c=0) at
/ext/R/cvs/R-devel/src/main/gram.y:1673
#4 0x080aad30 in token () at /ext/R/cvs/R-devel/src/main/gram.y:1744
#5 0x080ab12a in Rf_yylex () at /ext/R/cvs/R-devel/src/main/gram.y:1886
#6 0x080a89f4 in Rf_yyparse () at
/usr/local/share/bison/bison.simple:595
#7 0x080a9afd in R_Parse1 (status=0x46)
at /ext/R/cvs/R-devel/src/main/gram.y:948
#8 0x080a9e1e in R_Parse (n=-1, status=0xbfffcdf8)
at /ext/R/cvs/R-devel/src/main/gram.y:1083
#9 0x080a9fa3 in R_ParseConn (con=0x1, n=-1, status=0xbfffcdf8)
at /ext/R/cvs/R-devel/src/main/gram.y:1147
#10 0x08117b61 in do_parse (...
2008 May 13
2
(PR#11281) Bug in R 2.7 for over long lines (crasher+proposed fix!)
>>>>> "BDR" == Prof Brian Ripley <ripley at stats.ox.ac.uk>
>>>>> on Tue, 13 May 2008 07:32:43 +0100 (BST) writes:
BDR> This example does not crash in R 2.7.0, R-patched nor
BDR> R-devel (r45677) for me (x86_64 F8 Linux.) It also
BDR> does not crash with the CRAN build of R 2.7.0 on
BDR> Windows XP.
Neither does it
2009 Sep 16
4
2.10.0 Under development (unstable) (2009-09-15 r49711) just built segfaults on Debian Squeeze
I just downloaded R-devel and when loaded it immediately segfaults. I'm not
sure how much or what sort of diagnostic info and can provide, but below is
my build script, my console output, and the output of uname -r. I am
currently dependent on the development version of a package, so I'd like to
get R-devel up and running if possible. I am sure there is more info I can
provide, but before