search for: do_readlines

...connections.c:2094: structure has no member named `open64' connections.c: In function `do_unz': connections.c:2145: structure has no member named `open64' connections.c: In function `do_open': connections.c:2192: structure has no member named `open64' connections.c: In function `do_readLines': connections.c:2462: structure has no member named `open64' connections.c: In function `do_writelines': connections.c:2556: structure has no member named `open64' connections.c: In function `do_readbin': connections.c:2692: structure has no member named `open64' connections...

...ntry points into CHARSXPs if that were desired. Finally, this signed char business hints at a potential broader issue. If I understand correctly importing byte sequences with values greater than 0x7f overflows the `char` buffers on systems with signed chars and octet (or lesser) bytes, e.g. as in `do_readLines`[6] where an integer procured via `fgetc` is subsequently stored in a `char` buffer.? Obviously this hasn't mattered much to date, presumably because the implementations R runs on define the `unsigned char` to `signed char` conversion in such a way that the `signed char` to `unsigned char` conv...

I'm wondering if anyone has written some functions or code for handling very large files in R. I am working with a data file that is 41 variables times who knows how many observations making up 27MB altogether. The sort of thing that I am thinking of having R do is - count the number of lines in a file - form a data frame by selecting all cases whose line numbers are in a supplied vector