Re: [Rd] No R-2.14 beta executable for windows?

2011-10-18 Thread peter dalgaard
On Oct 19, 2011, at 07:52 , Dan Tenenbaum wrote: > The link to the installer exe here: > > http://cran.fhcrc.org/bin/windows/base/rtest.html > > ...has been broken for a couple days? > Looks like a local mirroring issue, CRAN master works, so does the .dk mirror. Getting cutting-edge tes

[Rd] No R-2.14 beta executable for windows?

2011-10-18 Thread Dan Tenenbaum
The link to the installer exe here: http://cran.fhcrc.org/bin/windows/base/rtest.html ...has been broken for a couple days? Thanks Dan __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Hervé Pagès
On 11-10-18 04:00 PM, Kevin Wright wrote: Hadley, Any chance of changing fun.aggregate to FUN and value_var to value.var? aggregate(.., FUN, ...) acast(..., fun.aggregate, ...) cast(..., value.var) acast(..., value_var) Side note: My fantasy for R 3.0 would be to fix the obvious inconsistenci

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Kevin Wright
Hadley, Any chance of changing fun.aggregate to FUN and value_var to value.var? aggregate(.., FUN, ...) acast(..., fun.aggregate, ...) cast(..., value.var) acast(..., value_var) Side note: My fantasy for R 3.0 would be to fix the obvious inconsistencies in function names/arguments, use Roxygen

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Kevin Wright
Not only is it fun to think about a generic load function, I created one and it is a pleasure to use--avoids the inconsistent function names that prompted your post. What's more important, language purity (S3 methods) or making life simpler for the users (consistency)? This "import" is not a true

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Hadley Wickham
>> Ending names in .foo is a bad idea because of the S3 naming conventions, so >> I think this is unlikely.  But you can always create an alias yourself... > > I always thought that S3 was part of the reason for read.ext write.ext. In: > > "/path/file.ext" > > the "class" of the file is "ext".  I k

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Joshua Wiley
On Tue, Oct 18, 2011 at 9:34 AM, Duncan Murdoch wrote: > On 18/10/2011 9:37 AM, Hadley Wickham wrote: >> >> Hi all, >> >> Is there any chance that readRDS and saveRDS might one day become >> read.rds and write.rds?  That would make them more consistent with the >> other reading and writing functio

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Geoff Jentry
On Tue, 18 Oct 2011, Hadley Wickham wrote: * read.csv and write.csv * load and save * readRDS and saveRDS Even loadRDS/saveRDS or readRDS/writeRDS would be better than the current combo. You could change the CSV functions to readCSV and writeCSV :)

Re: [Rd] Creating a package skeleton with no flesh

2011-10-18 Thread Hervé Pagès
On 11-10-15 05:50 AM, Duncan Murdoch wrote: On 14/10/2011 7:51 PM, Hervé Pagès wrote: Hi, Wouldn't it be awesome if package.skeleton() could be used to produce, well... a package skeleton? In a fresh R session: Empty packages are almost identical, differing only in the name entry in the DESCR

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Duncan Murdoch
On 18/10/2011 12:37 PM, Hadley Wickham wrote: >> Is there any chance that readRDS and saveRDS might one day become >> read.rds and write.rds? That would make them more consistent with the >> other reading and writing functions. > > Ending names in .foo is a bad idea because of the S3 naming

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Gavin Simpson
On Tue, 2011-10-18 at 08:37 -0500, Hadley Wickham wrote: > Hi all, > > Is there any chance that readRDS and saveRDS might one day become > read.rds and write.rds? That would make them more consistent with the > other reading and writing functions. > > Hadley > I would hope not. Those would the

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Jeffrey Ryan
As load involves a side-effect, I would think that loadRDS is a bad idea. That said, read/write is far more consistent across all languages and internally with R than read/save is. My (worthless) vote is for writeRDS. Jeff On Tue, Oct 18, 2011 at 11:37 AM, Hadley Wickham wrote: >>> Is there an

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Hadley Wickham
>> Is there any chance that readRDS and saveRDS might one day become >> read.rds and write.rds?  That would make them more consistent with the >> other reading and writing functions. > > Ending names in .foo is a bad idea because of the S3 naming conventions, so > I think this is unlikely.  But you

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Duncan Murdoch
On 18/10/2011 9:37 AM, Hadley Wickham wrote: Hi all, Is there any chance that readRDS and saveRDS might one day become read.rds and write.rds? That would make them more consistent with the other reading and writing functions. Ending names in .foo is a bad idea because of the S3 naming convent

Re: [Rd] readRDS and saveRDS

2011-10-18 Thread Jeffrey Ryan
I'd second this. Though my thinking was to add writeRDS instead of saveRDS. Jeff On Tue, Oct 18, 2011 at 8:37 AM, Hadley Wickham wrote: > Hi all, > > Is there any chance that readRDS and saveRDS might one day become > read.rds and write.rds?  That would make them more consistent with the > othe

[Rd] readRDS and saveRDS

2011-10-18 Thread Hadley Wickham
Hi all, Is there any chance that readRDS and saveRDS might one day become read.rds and write.rds? That would make them more consistent with the other reading and writing functions. Hadley -- Assistant Professor / Dobelman Family Junior Chair Department of Statistics / Rice University http://ha