Re: [R] read.table(..., header == FALSE, colClasses = )

Yes, it makes sense now; lesson learned. Thank you both! Sometimes it seems that no matter how good the documentation, some useR will inevitably (ab)use the code in ways that were never intended by the authors. Then when the code and/or documentation changes, it is not always obvious to the

Re: [R] read.table(..., header == FALSE, colClasses = )

> Benjamin Tyner > on Tue, 24 Oct 2017 07:21:33 -0400 writes: > Jeff, > Thank you for your reply. The intent was to construct a minimum > reproducible example. The same warning occurs when the 'file' argument > points to a file on disk with a

Re: [R] read.table(..., header == FALSE, colClasses = )

Jeff, Thank you for your reply. The intent was to construct a minimum reproducible example. The same warning occurs when the 'file' argument points to a file on disk with a million lines. But you are correct, my example was slightly malformed and in fact gives an error under R version 3.2.2.

Re: [R] read.table(..., header == FALSE, colClasses = )

You are constructing the equivalent of a two-line data file, and complaining that it is not treating it like it was one line. If it did used to accept this silently [skeptical] then I for one am glad it produces a warning now. -- Sent from my phone. Please excuse my brevity. On October 23,

[R] read.table(..., header == FALSE, colClasses = )

Hello I noticed that starting with R version 3.3.0 onward, this generates a warning:    > txt <- c("a", "3.14")    > read.table(file = textConnection(txt), header = FALSE, colClasses = c(x = "character", y = "numeric")) the warning is "not all columns named in 'colClasses' exist" and I