Re: [Rd] Issue with getParserData in R3.0.0

2013-01-15 Thread Duncan Murdoch
On 13-01-14 7:49 PM, Brian Lee Yung Rowe wrote: Thanks that seems to work. It looks like other packages explicitly change this to FALSE, so I have to set this to TRUE for each function call. Is there any particular policy for packages that update this option? Should I restore the original valu

Re: [Rd] Issue with getParserData in R3.0.0

2013-01-14 Thread Brian Lee Yung Rowe
Thanks that seems to work. It looks like other packages explicitly change this to FALSE, so I have to set this to TRUE for each function call. Is there any particular policy for packages that update this option? Should I restore the original value upon function exit? Warm Regards, Brian On Ja

Re: [Rd] Issue with getParserData in R3.0.0

2013-01-14 Thread Duncan Murdoch
On 13-01-13 8:43 PM, Brian Lee Yung Rowe wrote:> Hello, > > I am migrating my package lambda.r to R3.0.0 and am experiencing some issues with the getParserData function (which replaces the parser package). Basically the function works in the R shell but fails when either called from RUnit or fr

[Rd] Issue with getParserData in R3.0.0

2013-01-14 Thread Brian Lee Yung Rowe
Hello, I am migrating my package lambda.r to R3.0.0 and am experiencing some issues with the getParserData function (which replaces the parser package). Basically the function works in the R shell but fails when either called from RUnit or from R CMD check. I've narrowed it down to the functi