Re: [Rd] R CMD check in R-3.0.0 gives warnings

2013-03-22 Thread Duncan Murdoch
On 13-03-22 4:40 PM, Berend Hasselman wrote: On 22-03-2013, at 21:26, Dirk Eddelbuettel wrote: On 22 March 2013 at 21:03, Berend Hasselman wrote: | I am running R CMD check on my package nleqslv with R-3.0.0 beta (2013-03-33 r62364) on Mac OS X 10.6.8 | | In contrast with R-2.15.3 R CMD che

Re: [Rd] R CMD check in R-3.0.0 gives warnings

2013-03-22 Thread Berend Hasselman
On 22-03-2013, at 21:26, Dirk Eddelbuettel wrote: > > On 22 March 2013 at 21:03, Berend Hasselman wrote: > | I am running R CMD check on my package nleqslv with R-3.0.0 beta > (2013-03-33 r62364) on Mac OS X 10.6.8 > | > | In contrast with R-2.15.3 R CMD check now issues a note for > | > |

Re: [Rd] R CMD check in R-3.0.0 gives warnings

2013-03-22 Thread Dirk Eddelbuettel
On 22 March 2013 at 21:03, Berend Hasselman wrote: | I am running R CMD check on my package nleqslv with R-3.0.0 beta (2013-03-33 r62364) on Mac OS X 10.6.8 | | In contrast with R-2.15.3 R CMD check now issues a note for | | - Mercurial version control files .hgignore, .hgtags and directory .h

[Rd] R CMD check in R-3.0.0 gives warnings

2013-03-22 Thread Berend Hasselman
I am running R CMD check on my package nleqslv with R-3.0.0 beta (2013-03-33 r62364) on Mac OS X 10.6.8 In contrast with R-2.15.3 R CMD check now issues a note for - Mercurial version control files .hgignore, .hgtags and directory .hg. These are however included in .hidden_file_exclusions. -

[Rd] Why does typeof() modify an object's "named" field?

2013-03-22 Thread Josh O'Brien
Hello, Doing typeof() on an object appears to reset the "named" field in its sxpinfo header to 2, which can change the way that subsequent subassignment operations are carried out: X <- 1:5e7 .Internal(inspect(X)) # @4eeb0008 13 INTSXP g0c7 [NAM(1)] (len=5000, tl=0) 1,2,3,4,5,... system.time

Re: [Rd] read.pnm question in R-beta

2013-03-22 Thread Prof Brian Ripley
On 22/03/2013 17:53, Hodgess, Erin wrote: In R-beta (Masked Marvel), when I do the example from the read.pnm help file, this is what happens: x <- read.pnm(system.file("pictures/logo.pgm",package="pixmap")[1]) Warning message: In rep(cellres, length=2): x is NULL so the result will be NULL In

Re: [Rd] read.pnm question in R-beta

2013-03-22 Thread peter dalgaard
On Mar 22, 2013, at 18:53 , Hodgess, Erin wrote: > In R-beta (Masked Marvel), when I do the example from the read.pnm help file, > this is what happens: > > x <- read.pnm(system.file("pictures/logo.pgm",package="pixmap")[1]) > Warning message: > > In rep(cellres, length=2): x is NULL so the re

[Rd] read.pnm question in R-beta

2013-03-22 Thread Hodgess, Erin
In R-beta (Masked Marvel), when I do the example from the read.pnm help file, this is what happens: x <- read.pnm(system.file("pictures/logo.pgm",package="pixmap")[1]) Warning message: In rep(cellres, length=2): x is NULL so the result will be NULL In R-2.15.3, it's all right. Thanks, Erin Eri

Re: [Rd] Description depends line for windows only

2013-03-22 Thread Dirk Eddelbuettel
On 22 March 2013 at 10:44, Andrew Redd wrote: | I am developing a package that is only applicable on windows, is there a | line I can put in the depends field of the DESCRIPTION file to tell that | this should only be build for windows? There is a different field for this. From Section 1.1.1 of y

Re: [Rd] Description depends line for windows only

2013-03-22 Thread Dan Tenenbaum
On Fri, Mar 22, 2013 at 9:44 AM, Andrew Redd wrote: > I am developing a package that is only applicable on windows, is there a > line I can put in the depends field of the DESCRIPTION file to tell that > this should only be build for windows? > OS_type: windows See RShowDoc("R-exts") Section 1

[Rd] Description depends line for windows only

2013-03-22 Thread Andrew Redd
I am developing a package that is only applicable on windows, is there a line I can put in the depends field of the DESCRIPTION file to tell that this should only be build for windows? Are there any other protocols that I should follow? Thanks, -- Andrew May the Open Source be with you.

Re: [Rd] Deprecating partial matching in $.data.frame

2013-03-22 Thread Hervé Pagès
Hi, On 03/22/2013 01:31 AM, peter dalgaard wrote: On Mar 22, 2013, at 05:57 , Hervé Pagès wrote: Hi, Maybe a compromise would be to just issue a warning without deprecating? That way people who want to do anova(fit1)$P can still do it. When working interactively, it's certainly convenient (s

Re: [Rd] ess completion

2013-03-22 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/03/13 13:30, Terry Therneau wrote: > The thread is strange to me as well, since completion is logically impossible > for my Sweave > files. - an emacs buffer is open working on an .Rnw file - there is no copy > of R running > anywhere on the ma

[Rd] ess completion

2013-03-22 Thread Terry Therneau
The thread is strange to me as well, since completion is logically impossible for my Sweave files. - an emacs buffer is open working on an .Rnw file - there is no copy of R running anywhere on the machine - the code chunk in the .Rnw file refers to a R data object saved somewhere els

Re: [Rd] Deprecating partial matching in $.data.frame

2013-03-22 Thread peter dalgaard
On Mar 22, 2013, at 05:57 , Hervé Pagès wrote: > Hi, > > Maybe a compromise would be to just issue a warning without > deprecating? That way people who want to do anova(fit1)$P can > still do it. When working interactively, it's certainly convenient > (serious code however should probably stay a