The consensus is that it is a very bad idea for a file nominally described as a
CSV file to have a varying numbers of fields from record to record. If you have
need for such a file and go to whatever lengths you need to in order to create
it, please mark it as something other than a CSV file
I'm not sure if I have understood your question, so I will put two
possibilities:
1 - You have a variable called X =0 and a variable called Y = 12 and
want that to be numeric. You can do this:
X - as.numeric(X)
Y - as.numeric(Y)
2 - You have a variable called XY = 0,12 and want to make a
Ben Bolker bbol...@gmail.com
on Thu, 15 Sep 2011 11:03:26 +0200 writes:
Inspired by
http://stackoverflow.com/questions/7487778/could-you-tell-me-what-this-error-means
I wrote the following very small (one-line) patch which
returns an *informative* error message when R
On 09/28/2011 09:23 AM, Mehmet Suzen wrote:
This might be obvious but I was wondering if anyone knows quick and easy
way of writing out a CSV file with varying row lengths, ideally an
initial data read from a CSV file which has the same format. See example
below.
I found it quite strange that
Mehmet Suzen msuzen at mango-solutions.com writes:
This might be obvious but I was wondering if anyone knows quick and easy
way of writing out a CSV file with varying row lengths, ideally an
initial data read from a CSV file which has the same format. See example
below.
Hi folks,
I've attached a patch to the svn trunk that improves the performance
of the serialize/unserialize interface for vector types. The current
implementation: a) invokes the R_XDREncode operation for each element
of the vector type, and b) uses a switch statement to determine the
stream type
