Displaying 6 results from an estimated 6 matches for "r_unserialize".
2007 Aug 23
3
RData File Specification?
...ata file to a delimited text file. The data frame is too large to load() and extract rows from on a typical PC. I'm looking to parse through the file and extract individual entries without loading the whole thing into memory.
In terms of some C source functions, instead of doing RestoreToEnv(R_Unserialize(connection)) which is essentially what load() does, I'm looking to get the documentation I would need to build a function "SaveToCSV()" so that I could do SaveToCSV(R_Unserialize(connection)).
Where can I get documentation on the RData file format? Does a spec document exist?
See d...
2012 Mar 22
1
Serializing many small objects efficiently
...trying to write a serialization function for a format called
typedbytes, which is used as an interchange format in Hadoop circles. Since
I would need to serialize according to the internal R format many small R
objects I looked at the c interface
void R_Serialize(SEXP s, R_outpstream_t ops);
SEXP R_Unserialize(R_inpstream_t ips);
If I look at the source for e.g. unserialize is see a
.Call("R_unserialize", connection, refhook, PACKAGE = "base")
which, despite the name of the second argument, accepts as 'connection' a
raw vector. Is there any way to call that function from C...
2008 Jul 31
2
C versions of serialize/unserialize in packages
Are the functions 'R_Unserialize' and 'R_InitFileInPStream' allowed to
be used in R packages? I guess I'm just not clear on the implications
of this comment in 'Rinternals.h':
/* The connection interface is not yet available to packages. To
allow limited use of connection pointers this defines the opa...
2011 Dec 06
1
unserialize and eager execution
...mething unusual
- call to unserialize() resulted in
an error about loading a namespace.
I was a bit taken back by this - why should unserializing an object cause a
namespace lookup?
Are there any other side-effects of unserialize() that I should be cautious
about? I've been
digging through the R_Unserialize() call, I haven't found the loadNamespace
bit yet but I
assume its in there somewhere.
Is there anyway to guard against R eagerly evaluating serialized data
(serialize()) being unserialized (unserialize()) ?
Thanks,
Tyler
[[alternative HTML version deleted]]
2012 Nov 20
1
Buffer overflow in date package
Dear list-members,
I have observed quite a strange problem with the date package.
You will find below what I get on my machine (Ubuntu). I have been able to
reproduce the error on Red Hat too. But it seems not to happen on Windows
(and on some other Linux distros?).
> require(date)
Loading required package: date
> sessionInfo()
R version 2.15.2 (2012-10-26)
Platform: x86_64-pc-linux-gnu
2006 Oct 02
0
2.3.1: interacting bugs in load() and gzfile() (PR#9271)
...========
PATCHES:
for bug 1:
diff -u R-2.3.1.original/src/main/saveload.c R-2.3.1/src/main/saveload.c
--- R-2.3.1.original/src/main/saveload.c 2006-04-09 18:19:51.000000000 -0400
+++ R-2.3.1/src/main/saveload.c 2006-10-02 13:10:21.000000000 -0400
@@ -2301,6 +2301,7 @@
PROTECT(res = RestoreToEnv(R_Unserialize(&in), aenv));
if (wasopen) {
endcontext(&cntxt);
+ } else {
con->close(con);
}
UNPROTECT(1);
for bug 2:
diff -u R-2.3.1.original/src/main/connections.c R-2.3.1/src/main/connections.c
--- R-2.3.1.original/src/main/connections.c 2006-05-18 05:13:54.000000000 -04...