In response to the Aug 20 posting by Vadim, I had the same issue with
all kinds of complaints about row.names when it was not given in the
read.table command; when it was set to NULL (data were actually
shifted to the wrong names). I believe the problem was no comma (or
specified delimiter) at
On Mon, 17 Apr 2006, Martin Maechler wrote:
> Thanks a lot, Brian,
> I've been very happy with your proposal, but haven't yet looked
> at the details of the R-devel implementation.
> The NEWS entry only mentions *integer* rownames as new feature -
> which is exact from the user's perspective as yo
Thanks a lot, Brian,
I've been very happy with your proposal, but haven't yet looked
at the details of the R-devel implementation.
The NEWS entry only mentions *integer* rownames as new feature -
which is exact from the user's perspective as you emphasize
below. It might be worth mentioning that
On Mon, 17 Apr 2006, Don MacQueen wrote:
> This looks like a good proposal to me, from an end-user's point of view.
>
> I have, from time to time, wished I could set row names to NULL. Not for
> performance reasons, but because some aspect of my data, in combination with
> how R handles row name
This looks like a good proposal to me, from an end-user's point of view.
I have, from time to time, wished I could set row names to NULL. Not
for performance reasons, but because some aspect of my data, in
combination with how R handles row names, was requiring me to
explicitly manage them in s
