[Rd] parse():ing a unclosed string

2005-08-14 Thread Henrik Bengtsson
When parse():ing R code from *file* with a unclosed string, that is, a string that has an open quoation mark, but not a ending one, the string seems to be closed automagically. Is this a "bug"? Example: > code <- "x <- '123"; > parse(text=code) # Gives an error as expected Error in

[Rd] make check-all fails (PR#8063)

2005-08-14 Thread jed
Full_Name: Jed Kaplan Version: 2.1.1 Patched OS: Fedora Core 4 Submission from: (NULL) (66.31.221.212) Installation through "make check" succeeds. "Make check-all" fails with the following tail message: " make[3]: Entering directory `/mnt/linuxApp/usr/local/R/R-patched/tests' running code in 'p-r

[Rd] documentation for eval() typo

2005-08-14 Thread Paul Roebuck
>It is equivalent to 'evalq' except the its default ^^^ > R.version.string [1] "R version 2.1.1, 2005-06-20" -- SIGSIG -- signature too long (core dumped) __ R-

Re: [Rd] make check-all fails (PR#8063)

2005-08-14 Thread ripley
Please do read the docs: this test is randomm and will fail about 1 in 50 and if you have already run make check, you have already passed it. Definitely no bug in R. On Sun, 14 Aug 2005 [EMAIL PROTECTED] wrote: > Full_Name: Jed Kaplan > Version: 2.1.1 Patched > OS: Fedora Core 4 > Submission fr

Re: [Rd] parse():ing a unclosed string

2005-08-14 Thread Prof Brian Ripley
On Sun, 14 Aug 2005, Henrik Bengtsson wrote: > When parse():ing R code from *file* with a unclosed string, that is, a > string that has an open quoation mark, but not a ending one, the string > seems to be closed automagically. Is this a "bug"? It's clearly intentional from the comments in the s

Re: [Rd] documentation for eval() typo

2005-08-14 Thread Prof Brian Ripley
Thank you. It would be easier to deal with thes reports if in future you could provide a patch against the source file (here eval.Rd). On Sun, 14 Aug 2005, Paul Roebuck wrote: >> It is equivalent to 'evalq' except the its default -- Brian D. Ripley, [EMAIL PROTECTED] Professo