Re: [R] non-terminal token lacking children from utils::getParseData

2015-05-02 Thread Benjamin Tyner
Thank you Yihui for also reporting the bug here: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16354 and thank you Duncan for finding the issue and fixing it! I definitely like your idea to report a summary message instead of the long text string. Regards Ben > I tried to reduce the offen

Re: [R] non-terminal token lacking children from utils::getParseData

2015-02-19 Thread Benjamin Tyner
I tried to reduce the offending portion as best I could to a more-or-less minimal example (1136 bytes), which can be downloaded via: wget https://www.dropbox.com/s/74rgxr5x2aalr99/badstring.R then once in R, > b <- parse(file = "~/badstring.R", keep.source = TRUE) > d <- getParseData

Re: [R] non-terminal token lacking children from utils::getParseData

2015-02-19 Thread Duncan Murdoch
On 19/02/2015 6:31 PM, B Tyner wrote: > Hi, > > I have run across a source file for which the return value > of getParseData() includes a record having FALSE for $terminal, yet it is > not the parent of any other tokens. Before I spend time constructing a > reproducible example, I wanted to verify

[R] non-terminal token lacking children from utils::getParseData

2015-02-19 Thread B Tyner
Hi, I have run across a source file for which the return value of getParseData() includes a record having FALSE for $terminal, yet it is not the parent of any other tokens. Before I spend time constructing a reproducible example, I wanted to verify that this is in fact unexpected behavior (under R