Re: [Rd] parse():ing a unclosed string
Prof Brian Ripley wrote:
> 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 sources: EOF during
> parsing is treated specially.
>
> Generally the parser has not been written to find all syntactic errors:
> in any case one would need a formal language definition to do that.
> Prior to R-devel quite a few mal-formed constants were accepted, for
> example.
>
>> Example:
>>
>> > code <- "x <- '123";
>> > parse(text=code) # Gives an error as expected
>> Error in parse(file, n, text, prompt) : parse error
>>
>> > cat(file="foo.R", code)
>
>
> What exactly is in this file?
I'm write the contents of character variable 'code' to file 'foo.R',
that is, I'm generating a file containing the nine characters "x <-
'123", then parsing it below.
>
>> > expr <- parse("foo.R") # Closes the open string
>> > print(expr)
>> expression(x <- "123\n")
>>
>> Parsing from stdin(), that is parse(), gives an error too.
>
>
> Those are _not_ the same thing. I am not clear what you actually tried,
> as you cannot generate an EOF this way.
> parse()
?x <- '123
Error in parse(file, n, text, prompt) : parse error
>
where press ENTER directly after "123". I'm not exactly sure what is
happen when I press enter and when or if a EOF is generated, but this
was the only test I did for stdin().
>
>> Platform: Windows XP Pro SP2, R Version 2.1.1 Patched (2005-07-20) as
>> well as R Version 2.2.0 Under development (unstable) (2005-07-19 r34991).
>
>
> These are rather old for non-released versions: there have been many
> changes since then (especially in R-devel).
I know, but behind a 56k-modem (again) ;( and though was better to
report anything than nothing.
/Henrik
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Shutdown by to much data (PR#8065)
Full_Name: Jan Bentlage Version: 2.1.1 OS: Windows Submission from: (NULL) (212.62.93.226) I loaded a huge database (textfile, semikolon seperated) by read.csv2. The data already appeared in the list (by ls()). When I want to view the data in the editor, R completly crashes. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Shutdown by to much data (PR#8065)
This is probably a bug in the editor, but you have given us no way to reproduce it. Please see the posting guide and FAQ and give us a reproducible example. On Mon, 15 Aug 2005 [EMAIL PROTECTED] wrote: > Full_Name: Jan Bentlage > Version: 2.1.1 > OS: Windows > Submission from: (NULL) (212.62.93.226) > > > I loaded a huge database (textfile, semikolon seperated) by read.csv2. The > data > already appeared in the list (by ls()). When I want to view the data in the > editor, R completly crashes. Which means what, exactly? Again, see the posting guide. -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] png and resolution (PR#8066)
Full_Name: Knut krueger Version: 2.1.1 OS: xp Home Submission from: (NULL) (149.225.134.34) In the png function the value res seems to be inactive: bmp(filename = "c:/r/Rplot%03d.bmp", width = 1920, height = 1920, pointsize = 48, bg = "white", res = 2400) result: witdh/heigth = 1920 <> 20.32 mm ppi=2400 Results as expected png(filename = "c:/r/Rplot%03d.png", width = 1920, height = 1920, pointsize = 48, bg = "white", res = 2400) witdh/heigth = 1920 <> 20.32 mm ppi=150 Result not as expected. __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] png and resolution (PR#8066)
Where did you get `result' from? (What program spells that badly and where does ppi come from?) Your last example gives for me (using ImageMagick) identify -format "%wx%h res: %x" Rplot001.png 1920x1920 res: 944.88 PixelsPerCentimeter which is correct. I believe it is your PNG reader that is buggy, not R. On Mon, 15 Aug 2005 [EMAIL PROTECTED] wrote: > Full_Name: Knut krueger > Version: 2.1.1 > OS: xp Home > Submission from: (NULL) (149.225.134.34) > > > In the png function the value res seems to be inactive: > > bmp(filename = "c:/r/Rplot%03d.bmp", width = 1920, height = 1920, pointsize = > 48, bg = "white", res = 2400) > result: > witdh/heigth = 1920 <> 20.32 mm > ppi=2400 > Results as expected > > > png(filename = "c:/r/Rplot%03d.png", width = 1920, height = 1920, pointsize = > 48, bg = "white", res = 2400) > > witdh/heigth = 1920 <> 20.32 mm > ppi=150 > Result not as expected. > > __ > R-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > > -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UKFax: +44 1865 272595 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Shutdown by to much data (PR#8065)
[EMAIL PROTECTED] wrote: > Full_Name: Jan Bentlage > Version: 2.1.1 > OS: Windows > Submission from: (NULL) (212.62.93.226) > > > I loaded a huge database (textfile, semikolon seperated) by read.csv2. The > data > already appeared in the list (by ls()). When I want to view the data in the > editor, R completly crashes. Please put together a reproducible example. This might be a data editor bug or a bug in read.csv2 or something specific to your system. For example, create a data.frame of the same size containing simulated values, then see if you can edit that. If you can, write it out to a file, and see if you can read it in. A bug report that is as vague as yours isn't likely to be acted on. Duncan Murdoch __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] Patches (was Re: documentation for eval() typo)
On Sun, 14 Aug 2005, Prof Brian Ripley wrote:
> On Sun, 14 Aug 2005, Paul Roebuck wrote:
>
> >> It is equivalent to 'evalq' except the its default
>
> It would be easier to deal with thes reports if in future you
> could provide a patch against the source file (here eval.Rd).
I normally download a copy of the current binary and the
matching source distribution for performing searches, so
would not be tracking r-devel or r-patched updates.
Would the following have been palatable as annotated?
R-2.1.1/src/library/base/man/eval.Rd:
59c59
< equivalent to \code{evalq} except that its default argument creates a
---
> equivalent to \code{evalq} except the its default argument creates a
--
SIGSIG -- signature too long (core dumped)
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Patches (was Re: documentation for eval() typo)
On Mon, 15 Aug 2005, Paul Roebuck wrote:
> On Sun, 14 Aug 2005, Prof Brian Ripley wrote:
>
>> On Sun, 14 Aug 2005, Paul Roebuck wrote:
>>
It is equivalent to 'evalq' except the its default
>>
>> It would be easier to deal with thes reports if in future you
>> could provide a patch against the source file (here eval.Rd).
>
> I normally download a copy of the current binary and the
> matching source distribution for performing searches, so
> would not be tracking r-devel or r-patched updates.
>
> Would the following have been palatable as annotated?
Yes, it would have been easy to incorporate.
> R-2.1.1/src/library/base/man/eval.Rd:
> 59c59
> < equivalent to \code{evalq} except that its default argument creates a
> ---
>> equivalent to \code{evalq} except the its default argument creates a
--
Brian D. Ripley, [EMAIL PROTECTED]
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UKFax: +44 1865 272595
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
