Dear Stepan, Thanks for your questions. I'll take a look at them over the next few days and get back to you with some answers. I've also opened a new issue on Github (https://github.com/grimbough/rhdf5/issues/10) with your question, so I'll post any replies there too.
Thanks, Mike On 28 February 2018 at 15:48, Stepan Kasal <ka...@ucw.cz> wrote: > Hello, > I believe I noticed two bugs in rhdf5. > > I'm using R 3.3.3 on Windows64, 2.18.0 linking to C-library HDF5 1.8.7 > > 1. problem: > > h5read(..., bit64conversion='double') > > converts int32 columns to double as well. I did not expect that the > option would affect 64bit integer types only. > Is this intentional? > Is it documented? > > 2. problem: > > AFAIK -2^63 of type int64 is not a number, it encodes NA. > I would expect that even with bit64conversion='double' or 'int', this > special value silently becomes NA. > (Or am I wrong? Is this convention generally accepted?) > > The warnings "integer precision lost" or "integer overflow" (respectively), > that are triggered by values that are in abs >= 2^53 or >= 2^31 (resp.), > should not be triggered by this special value. > > Thank you all for the package, > Stepan Kasal > > _______________________________________________ > Biocemail@example.com mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > [[alternative HTML version deleted]] _______________________________________________ Biocfirstname.lastname@example.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel