Re: [Rd] delete.response leaves response in attribute dataClasses

2012-01-06 Thread William Dunlap
> -Original Message- > From: Paul Johnson [mailto:pauljoh...@gmail.com] > Sent: Friday, January 06, 2012 11:17 AM > To: William Dunlap > Cc: R Devel List > Subject: Re: [Rd] delete.response leaves response in attribute dataClasses > > Thanks, Bill > > Counte

Re: [Rd] delete.response leaves response in attribute dataClasses

2012-01-06 Thread Paul Johnson
Thanks, Bill Counter-arguments at the end On Thu, Jan 5, 2012 at 3:15 PM, William Dunlap wrote: > My feeling that everyone would index dataClasses by name was > wrong.  I looked through the packages that used dataClasses > and saw code that would break if the first (response) entry > were omitte

Re: [Rd] delete.response leaves response in attribute dataClasses

2012-01-05 Thread William Dunlap
BCO Software wdunlap tibco.com > -Original Message- > From: r-devel-boun...@r-project.org [mailto:r-devel-boun...@r-project.org] On > Behalf Of William Dunlap > Sent: Thursday, January 05, 2012 12:57 PM > To: Paul Johnson; R Devel List > Subject: Re: [Rd] delete.response

Re: [Rd] delete.response leaves response in attribute dataClasses

2012-01-05 Thread William Dunlap
I had noticed the same thing but figured that most people (writers of predict methods) would be looking up entries in dataClasses by name and not by position, since predict's newdata argument need not have entries in the same order as the data used to fit the model. Hence the extra entry would not