From murdoch.duncan at gmail.com  Tue Oct 18 18:56:59 2011
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Tue, 18 Oct 2011 12:56:59 -0400
Subject: [Rd] readRDS and saveRDS
In-Reply-To: <CABdHhvHUw8D_ejfaxmkUqtB7hZ-F595TuZVBre2D9_az1UcgfA@mail.gmail.com>
References: <CABdHhvFEpU2zjcV+_Xd_vzrcM__VZ2PMSUgjKCHGYm38Xh+W2w@mail.gmail.com>
	<4E9DAA89.7050601@gmail.com>
	<CABdHhvHUw8D_ejfaxmkUqtB7hZ-F595TuZVBre2D9_az1UcgfA@mail.gmail.com>
Message-ID: <4E9DAFDB.90700@gmail.com>

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 conventions, so
> >  I think this is unlikely.  But you can always create an alias yourself...
>
> It just makes teaching that much harder.  We have the pairs:
>
> * read.csv and write.csv
> * load and save
> * readRDS and saveRDS
>
> Even loadRDS/saveRDS or readRDS/writeRDS would be better than the current combo.

Every problem is an opportunity.  Think of this as an example of why 
it's important to think about the names you give to functions.

Duncan Murdoch



[Rd] readRDS and saveRDS
Duncan Murdoch