Re: [Rd] subscripting a data.frame (without changing row order) changes internal row.names

2014-11-10 Thread Dr Gregory Jefferis
Hi Kevin, Joshua, Many thanks for this additional information. On 10 Nov 2014, at 22:21, Kevin Ushey wrote: I believe the question here is related to the sign on the compact row names representation: why is it sometimes `c(NA, )` and sometimes `c(NA, )` -- why the difference in sign? It was

Re: [Rd] subscripting a data.frame (without changing row order) changes internal row.names

2014-11-10 Thread Kevin Ushey
I believe the question here is related to the sign on the compact row names representation: why is it sometimes `c(NA, )` and sometimes `c(NA, )` -- why the difference in sign? To the best of my knowledge, older versions of R used the signed-ness of compact row.names to differentiate between diffe

Re: [Rd] subscripting a data.frame (without changing row order) changes internal row.names

2014-11-10 Thread Joshua Ulrich
On Mon, Nov 10, 2014 at 12:35 PM, Dr Gregory Jefferis wrote: > Dear R-devel, > > Can anyone help me to understand this? It seems that subscripting the rows > of a data.frame without actually changing their order, somehow changes an > internal representation of row.names that is revealed by e.g. >

[Rd] subscripting a data.frame (without changing row order) changes internal row.names

2014-11-10 Thread Dr Gregory Jefferis
Dear R-devel, Can anyone help me to understand this? It seems that subscripting the rows of a data.frame without actually changing their order, somehow changes an internal representation of row.names that is revealed by e.g. dput/dump/serialize I have read the docs and inspected the (R) code

Re: [Rd] R 3.1.1 and 3.1.2 both fail their test suites

2014-11-10 Thread Martin Maechler
> Duncan Murdoch > on Wed, 5 Nov 2014 10:22:09 -0500 writes: > On 05/11/2014 9:36 AM, Peter Simons wrote: >> Hi Duncan, >> >> > I don't think we should be removing tests for everybody to allow a few >> > people to test a build of R that none of us actually use.

Re: [Rd] ambiguity in the documented return value of Null() from package MASS

2014-11-10 Thread William Dunlap
> Presumably, the help file wording goes back to S-PLUS which > (to my recollection) didn't allow zero-extent matrices. Splus (and S) started having reasonable support for zero-extent matrices in May 2001 (i.e., Splus 6.0, which I think corresponds to S version 4-m of June 2, 1999), Splus5.0 (Nov

[Rd] Cursor not behaving properly

2014-11-10 Thread Kaiyin Zhong (Victor Chung)
I found a strange bug in R recently (version 3.1.2): As you can see from the screenshots attached, when the cursor passes the right edge of the console, instead of start on a new line, it goes back to the beginning of the same line, and overwrites everything after it. This happens every time the

Re: [Rd] ambiguity in the documented return value of Null() from package MASS

2014-11-10 Thread Martin Maechler
> peter dalgaard > on Mon, 10 Nov 2014 14:47:16 +0100 writes: > There is a maintainer for this contributed package... > However, a zero column vector _is_ numeric(0) -- with > dimension attributes c(3,0). > structure(numeric(0),dim=c(3,0)) > c(Null(diag(3)))

Re: [Rd] ambiguity in the documented return value of Null() from package MASS

2014-11-10 Thread peter dalgaard
There is a maintainer for this contributed package... However, a zero column vector _is_ numeric(0) -- with dimension attributes c(3,0). structure(numeric(0),dim=c(3,0)) c(Null(diag(3))) I.e., the ambiguity is pretty slight. Presumably, the help file wording goes back to S-PLUS which (to my

[Rd] ambiguity in the documented return value of Null() from package MASS

2014-11-10 Thread Georgi Boshnakov
Hi, Function Null from package MASS seems to return a matrix with zero columns and the expected number of rows when the null space of the argument contains only the zero vector, e.g. > library(MASS) > diag(nrow=3) [,1] [,2] [,3] [1,]100 [2,]010 [3,]001