On 27 November 2013 at 17:30, Murray Stokely wrote:
| I think none of these examples describe a zlib compressed data block inside a
| binary file that the OP asked about, as all of your examples are e.g.
| prepending gzip or zip headers.
Yes I fear I have no real idea what Greg is/was talking ab
I think none of these examples describe a zlib compressed data block inside
a binary file that the OP asked about, as all of your examples are e.g.
prepending gzip or zip headers.
Greg, is memDecompress what you are looking for?
- Murray
On Wed, Nov 27, 2013 at 5:22 PM, Dirk Eddelbue
On 27 November 2013 at 18:38, Dirk Eddelbuettel wrote:
|
| On 27 November 2013 at 23:49, Dr Gregory Jefferis wrote:
| | I have a binary file type that includes a zlib compressed data block (ie
| | not gzip). Is anyone aware of a way using base R or a CRAN package to
| | decompress this kind of
On 27 November 2013 at 23:49, Dr Gregory Jefferis wrote:
| I have a binary file type that includes a zlib compressed data block (ie
| not gzip). Is anyone aware of a way using base R or a CRAN package to
| decompress this kind of data (from disk or memory). So far I have found
| Rcompression::d
Hello,
I have a binary file type that includes a zlib compressed data block (ie
not gzip). Is anyone aware of a way using base R or a CRAN package to
decompress this kind of data (from disk or memory). So far I have found
Rcompression::decompress on omegahat, but I would prefer to keep
depend
On 27/11/2013 18:45, Simon Urbanek wrote:
On Nov 27, 2013, at 12:36 PM, wokai wrote:
I was recently challenged to correct my package source (rbamtools) because
there were issues reported by address sanitizer.
Therefore the problem of installing and running instrumented (R +) package
code aris
On Nov 27, 2013, at 12:36 PM, wokai wrote:
> I was recently challenged to correct my package source (rbamtools) because
> there were issues reported by address sanitizer.
> Therefore the problem of installing and running instrumented (R +) package
> code arises.
>
> Regrettably up to now, I fou
I was recently challenged to correct my package source (rbamtools) because
there were issues reported by address sanitizer.
Therefore the problem of installing and running instrumented (R +) package
code arises.
Regrettably up to now, I found no way to use the address sanitizer, neither
for a smal
> Laurent,
>
> blank lines between records are not allowed in DESCRIPTION, because
> they separate paragraphs in DCF and a package must consist of a single
> paragraph. This properly is used by R for multi-package DCF files
> where each paragraph defines one package. Blank lines at the end may
> b
