search for: encodeelement0

...which is bigger on machines that >> support big vectors. >> >> I haven't tested the change; there may be something else in that >> function that assumes short vectors. > Indeed, I think the function won't work for long vectors because of > EncodeElement2 and EncodeElement0. EncodeElement2/0 would have to be > changed, including their signatures That would be a definite fix but before such deep rewriting is undertaken may the following small fix (in addition to "(R_xlen_t)nr * nc") will be sufficient for cases where nr and nc are in int range but the...

...nes that >>> support big vectors. >>> >>> I haven't tested the change; there may be something else in that >>> function that assumes short vectors. >> Indeed, I think the function won't work for long vectors because of >> EncodeElement2 and EncodeElement0. EncodeElement2/0 would have to be >> changed, including their signatures > > That would be a definite fix but before such deep rewriting is > undertaken may the following small fix (in addition to "(R_xlen_t)nr * > nc") will be sufficient for cases where nr and nc ar...

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 this bug already reported about before: https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17182. However, there appears to be no solution or fixes in upcoming

...n't do that, x is a matrix of an atomic vector > type. VECTOR_ELT is taking elements of a generic vector, 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 s...

....? It should be R_xlen_t, which is bigger on machines that > support big vectors. > > I haven't tested the change; there may be something else in that > function that assumes short vectors. Indeed, I think the function won't work for long vectors because of EncodeElement2 and EncodeElement0. EncodeElement2/0 would have to be changed, including their signatures Tomas > > Duncan Murdoch > >> >> My version: >>> R.Version() >> $platform >> [1] "x86_64-w64-mingw32" >> >> $arch >> [1] "x86_64" >> >...