Re: [Rd] R 2.5.0 refuses to print enough digits to recover exact floating point values

2007-05-28 Thread Zack Weinberg
On 5/23/07, Prof Brian Ripley [EMAIL PROTECTED] wrote: [...] It really is the case that writing out a number to 15 significant digits and reading it back in again is not required to give exactly the same IEC60559 (sic) number, and furthermore there are R platforms for which this does not

Re: [Rd] [Bioc-devel] promptClass

2007-05-28 Thread Martin Maechler
MartinMo == Martin Morgan [EMAIL PROTECTED] on Sat, 26 May 2007 21:44:27 -0700 writes: MartinMo promptClass fails to identify methods associated MartinMo with the class. Here is a fix: Thank you, Martin; I've applied your patch to my working copy of R-devel, and I can confirm it

[Rd] Merge (PR#9699)

2007-05-28 Thread edward . m
Full_Name: Edward McNeil Version: 2.5.0 OS: Windows XP Submission from: (NULL) (203.170.234.5) This is a new bug introduced to R2.5.0. Scenario: If one of the data frames to merge contains two variables that have the same name, then the data in first variable (of the same name) is copied to

[Rd] When loading evir after evd, dgumbel gives an error (PR#9704)

2007-05-28 Thread r . r . p . vannooyen
Full_Name: Ronald van Nooijen Version: 1.4.1 and 1.5.0, evd 2.2-3 OS: windows xp Submission from: (NULL) (130.161.12.43) In an empty workspace first load package evd, then load package evir. a call to any of the routines dgumberl, qgumbel etcetera will now result in an error message of the form

Re: [Rd] Merge (PR#9699)

2007-05-28 Thread ripley
On Mon, 21 May 2007, [EMAIL PROTECTED] wrote: Full_Name: Edward McNeil Version: 2.5.0 OS: Windows XP Submission from: (NULL) (203.170.234.5) This is a new bug introduced to R2.5.0. Scenario: If one of the data frames to merge contains two variables that have the same name, then the data

Re: [Rd] When loading evir after evd, dgumbel gives an error (PR#9704)

2007-05-28 Thread Prof Brian Ripley
Please do not - report on ancient versions of R. - use R-bugs for reports on contributed packages. It is hard to see why you think this is a bug, but you could ask the authors of the two packages to work together to avoid this (or add namespaces to protect the packages against this). On Wed,

[Rd] How to correctly write a package?

2007-05-28 Thread Vladimir Eremeev
I am writing a package. Please, study the sequence of my actions below, and comment, what's incorrect. The package contains pure R code. 1. At the one level up from the package directory, from the system command prompt: R CMD build --binary ac9 This produces the file ac9_0.1.zip (The package

Re: [Rd] How to correctly write a package?

2007-05-28 Thread Uwe Ligges
Vladimir Eremeev wrote: I am writing a package. Please, study the sequence of my actions below, and comment, what's incorrect. The package contains pure R code. 1. At the one level up from the package directory, from the system command prompt: R CMD build --binary ac9 This produces

Re: [Rd] Merge (PR#9699)

2007-05-28 Thread edward . m
Yes, it appears to have been resolved in R2.5.0pat, although the counter-example provided *does* fail in R2.5.0. A - data.frame(x=1:3, y=4:6, y=7:9, check.names=FALSE) B - data.frame(x=1:3, a=3:1) A x y y 1 1 4 7 2 2 5 8 3 3 6 9 B x a 1 1 3 2 2 2 3 3 1 merge(A, B) x y y.1 a 1 1 4 4 3 2 2