search for: encodeinteg

Le 19/04/2018 ? 09:30, Tomas Kalibera a ?crit?: > On 04/19/2018 02:06 AM, Duncan Murdoch wrote: >> On 18/04/2018 5:08 PM, Tousey, Colton wrote: >>> Hello, >>> >>> I want to report a bug in R that is limiting my capabilities to >>> export a matrix with write.csv or write.table with over >>> 2,147,483,648 elements (C's int limit). I found

...1,2) factor(nums) # [1] 0.3 0.3 0.3 0.3 # Levels: 0.3 Petr. -------------- next part -------------- --- R-devel/src/main/coerce.c 2009-04-17 17:53:35.000000000 +0200 +++ R-devel-elim-trailing/src/main/coerce.c 2009-05-23 08:39:03.914774176 +0200 @@ -294,12 +294,33 @@ else return mkChar(EncodeInteger(x, w)); } +const char *elim_trailing(const char *s, char cdec) +{ + const char *p; + char *replace; + for (p = s; *p; p++) { + if (*p == cdec) { + replace = (char *) p++; + while ('0' <= *p & *p <= '9') { + if (*(p+...

...so it cannot be applied to "x". But even if we extracted a single element from "x" (e.g. via a type-switch etc), we would not be able to pass it to EncodeElement0 which expects a full atomic vector (that is, including its header). Instead we would have to call functions like EncodeInteger, EncodeReal0, etc on the individual elements. Which is then the same as changing EncodeElement0 or implementing a new version of it. This does not seem that hard to fix, just is not as trivial as changing the cast.. Tomas > > Serguei

...ied to "x". But even if we extracted a single element from "x" > (e.g. via a type-switch etc), we would not be able to pass it to > EncodeElement0 which expects a full atomic vector (that is, including > its header). Instead we would have to call functions like > EncodeInteger, EncodeReal0, etc on the individual elements. Which is > then the same as changing EncodeElement0 or implementing a new version > of it. This does not seem that hard to fix, just is not as trivial as > changing the cast.. Thanks Tomas for this detailed explanation. I would like also...