>> I meant what is the design principle behind check.names being hardcoded to
> FALSE.
>> I see no conflict with the purpose of cbind from the ability to specify
> check.names
>> at the level of cbind.
> Perhaps data.frame() should throw an error if there are duplicate names,
> or perhap
the output of
data.frame().
Is it worth the time to do that?
Bill Dunlap
Spotfire, TIBCO Software
wdunlap tibco.com
> -Original Message-----
> From: r-devel-boun...@r-project.org [mailto:r-devel-boun...@r-project.org] On
> Behalf
> Of Fg Nu
> Sent: Tuesday, July 23, 2013 10:48
> Is there then a reason that overriding the check.names default is forbidden
> from cbind? I can't tell why this would be the case.
For the same reason you can't have
data.frame(x=1:10, x=11:20, check.names=TRUE, check.names=FALSE)
or
mean(x=1:10, x=11:20)
i.e, you can't generally pass the
- Original Message -
From: Ista Zahn
To: Fg Nu
Cc: "r-devel@r-project.org"
Sent: Tuesday, July 23, 2013 11:05 PM
Subject: Re: [Rd] cbind error with check.names
On Tue, Jul 23, 2013 at 12:54 PM, Fg Nu wrote:
>
>
>
> - Original Message -
> From: Ist
- Original Message -
From: Ista Zahn
To: Fg Nu
Cc: "r-devel@r-project.org"
Sent: Tuesday, July 23, 2013 9:50 PM
Subject: Re: [Rd] cbind error with check.names
On Tue, Jul 23, 2013 at 9:18 AM, Fg Nu wrote:
>
>
>
> Here is an example where cbind fails with an
On Tue, Jul 23, 2013 at 12:54 PM, Fg Nu wrote:
>
>
>
> - Original Message -
> From: Ista Zahn
> To: Fg Nu
> Cc: "r-devel@r-project.org"
> Sent: Tuesday, July 23, 2013 9:50 PM
> Subject: Re: [Rd] cbind error with check.names
>
> On
On Tue, Jul 23, 2013 at 9:18 AM, Fg Nu wrote:
>
>
>
> Here is an example where cbind fails with an error when check.names=TRUE is
> set.
>
> data(airquality)
> airQualityBind =cbind(airquality,airquality,check.names =TRUE)
>
>
> I understand that cbind is a call to data.frame and the following w
