From fgnu32 at yahoo.com  Thu Jul 25 13:58:58 2013
From: fgnu32 at yahoo.com (Fg Nu)
Date: Thu, 25 Jul 2013 04:58:58 -0700 (PDT)
Subject: [Rd] cbind error with check.names
In-Reply-To: <E66794E69CFDE04D9A70842786030B931C328CF0@PA-MBX01.na.tibco.com>
References: <1374585525.97733.YahooMailNeo@web160105.mail.bf1.yahoo.com>	<CA+vqiLGkncU6QZm0CqBs+PbbXzFuGnzWvOOfrVqN9mUc4kttpQ@mail.gmail.com>	<1374598453.74044.YahooMailNeo@web160105.mail.bf1.yahoo.com>	<CA+vqiLHmAC2n-5kUTS+J09O8BzEvikLEyK+v2i3Kv3ffGGn2KA@mail.gmail.com>
	<1374601659.38463.YahooMailNeo@web160105.mail.bf1.yahoo.com>
	<E66794E69CFDE04D9A70842786030B931C328CF0@PA-MBX01.na.tibco.com>
Message-ID: <1374753538.31658.YahooMailNeo@web160101.mail.bf1.yahoo.com>





>>  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 perhaps it should have a separate argument to say what to do about duplicate 
> names,
> but changing that sort of thing now would break a fair bit of code.? Perhaps
> cbind.data.frame should not call data.frame, but copy the work that data.frame
> does or perhaps it should check for duplicate names on the output of 
> data.frame().
> Is it worth the time to do that?
> 



Bill, thanks for your reply. I understand that this is one of things that just are. For me, the ability to check for duplicate names in dataframes is important, and it is surprising that I never realised before that cbind has this limitation.



[Rd] cbind error with check.names
Fg Nu