similar to: read.table messes up stdin upon small, erroneous input (PR#7722)

Dear all, I discovered that read.table (RW1.8.0) leaves out data when reading multiple-line records. Replication code at the end Best regards Jens Oehlschlägel > filename <- "c:/tmp/c2.csv" > > data <- data.frame(a=c("c", "e\nnewline"), b=c("d", '"quoted simpleline"')) > > #look at the data >

One of the great things about R is how readable and re-usable much of its own implementation is. If an R function doesn't do quite what you want but is close, it is usually very easy to read its code and start adapting that as the base for a modified version. In the 2.x versions of R, that was the case with read.table(). It was easy to experiment with its source code, as it all worked just

I'm trying to write a Rscript program capable of reading several tables from the standard input. The problem is that the tables aren't in files because they are coming from another process that is generating them. From the R-console the following works pretty well: |> f <- stdin() |> t <- read.table(f) |> t2 <- read.table(f) |> t uno dos 01 3 4

The 'read.table' function appears to be up to 10X slower in R 1.4.0 than R 1.3.1 for some of the data sets I read in. I was comparing the source code for the 2 versions and see that it was rewritten in R 1.4.0. I think I found out what part of the problem might be. I was comparing R1.3.1 and R1.4.0 code and it appears that a statement is missing in some of the code for R 1.4. This is

Thanks a lot, James!! The problem is fixed. On the version 1.4.0 Mac/darwin (the latest available version for this system) the function read.table (which is called from read.delim etc., too) has the bug you explained. Inserting the row nlines <- nlines+1 after lines <- c(lines, line) removes this bug. M. On Friday, February 22, 2002, at 02:33 PM, james.holtman at convergys.com

Dear all, I just upgraded version of R to R 2.2.0, and I have a problem with a script that did not happen with my previous version. Here is the error : ----------------------------------------- > param<-read.table(file="param.dat",sep ="\t",header=TRUE,fill=TRUE, na.strings="NA") Erreur dans read.table.default(file = "param.dat", sep =

Hi all, I am running 64-bit R 2.15.0 on windows 7. I am trying to use read.delim to read from a file that has 2-byte unicode (CJK) characters. Here is an example of the data (it is tab-delimited if that gets messed up): HITId HITTypeId Title 2Q69Z6KW4ZMAGKKFRT6Q4ONO6MJF68 2LVJ1LY58B72OP36GNBHH16YF7RS7Z 看看句子，写写想法 请看以下的句子，再回答问 So read.delim (code below) doesn't read in correctly. It reads

Full_Name: Juho Vuori Version: 2.7.0 (2008-04-22) OS: Linux poseidon.fimr.fi 2.6.23.17-88.fc7PAE #1 SMP Thu May 15 00:22:53 EDT 2008 i686 i686 i386 GNU/Linux Submission from: (NULL) (193.166.188.194) Calling read.table() twice the following way causes a segmentation fault in R. Run R and type the following commands: > read.table(stdin()) 0: 1 2 3 1: 3 2: Error in scan(file, what, nmax, sep,

Dear all, is there a reason why the function readTableHead refers to itself in the error or warning messages as readTableHeader? lines 1590-1596 of scan.c : if(data.con->text && data.con->blocking) { warning(_("incomplete final line found by readTableHeader on '%s'"), data.con->description); } else error(_("incomplete final line found by

I've just implemented a generalization of R's text connections, to also support reading/writing raw binary data. There is very little new code to speak of. For input connections, I wrote code to populate the old text connection buffer from a raw vector, and provided a new raw_read() method. For output connections, I wrote a raw_write() to append to a raw vector. On input, the mode

Full_Name: Dr. Alex Sheppard Version: 2.7.1 OS: Linux Debian Lenny Submission from: (NULL) (79.73.224.62) After scanning from an open (text) connection, then seeking, then scanning again, the second scan returns incorrect result. It looks like the first byte scanned was from the pre-seek file position, then it continues to read from the post-seek file position. To reproduce: #Put 3x3 matrix

Is this the last bug of the year? Well, it's the last one from me, anyway... The "parse" function seems to give erratic behaviour when used in conjunction with "pushBack" on an open connection (R1.6.1, Windows 2000). Try this: > { cat( c( '1', 'a+b', '2'), file='r123.r', sep='\n'); tcon_ file( 'r123.r'); open( tcon);

Hi, I am wondering what the trick is to use InPlaceEditor on an emtpy div. I have a set up where one div contains a question, and next to it is an emtpy div which should be used for InPlaceEditor. The user clicks on a button "answer" and that activates the InPlaceEditor in the appropriate div. This doesn''t work, however. The div which should use InPlaceEditor must

https://bugzilla.samba.org/show_bug.cgi?id=10951 Bug ID: 10951 Summary: Emtpy parameter triggers unwanted behavior, but no error message Product: rsync Version: 3.1.0 Hardware: x64 OS: Linux Status: NEW Severity: major Priority: P5 Component: core Assignee:

The control flow was: if (!y) { ppix = ... } if (y) { ... } else if (x) { use ppix for something } else { use ppix for something } Merge the if(!y) block with the two else branches. This avoids a false-positive in the clang static analyzer, it can't know that !y and x are mutually exclusive. The result looks something like this: if (y) { ... } else { ppix = ... if (x) {

In a C++ extension to R (v 1.8.1), I've been experimenting with a generic "push back" function to tack one value at a time onto the end of an R vector created within the extension. After calling this function a certain number of times Rgui.exe (I'm writing in Windows using Visual Studio .NET 2003) will fail with an Access Violation, which doesn't happen when I pre-allocate

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --27464147-536455723-1259929222=:18586 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <alpine.LFD.2.00.0912041222341.18586 at gannet.stats.ox.ac.uk> It's not to do with pushback per

Full_Name: Kamil Barto? Version: 2.8.0 OS: windows xp Submission from: (NULL) (212.33.92.187) According to the "deparse" function documentation "nlines" is the *maximum* number of lines to produce. But, when "nlines" argument is supplied, it produces exactly nlines of result, and the result contains empty elements at the end. Example: >

I'm currently using the below function from some library (MASS?) for writing my data out to file. I'm using it instead of plain old "write" because it does buffering. The problem that I'm having is that the numbers are space padded, but I need true tab-delineated files. It looks like the spaces are coming from 'format', but I don't see an option for format to

On Sep 11, 2009, at 7:17 PM, Nick Lewycky wrote: > Dan Gohman wrote: >> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: >>> Devang's work on debug info prompted this, thoughts welcome: >>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt >> The document mentions "instructions" a lot. We'll want to be able to >> apply metadata to