On Thursday, 28 April 2016 at 20:12:58 UTC, Stefan Koch wrote:
On Wednesday, 27 April 2016 at 06:55:46 UTC, Walter Bright
wrote:
Sounds nice. I'm curious how it would compare to:
https://www.digitalmars.com/sargon/lz77.html
https://github.com/DigitalMars/sargon/blob/master/src/sargon/lz77.d
On Wednesday, 27 April 2016 at 06:55:46 UTC, Walter Bright wrote:
Sounds nice. I'm curious how it would compare to:
https://www.digitalmars.com/sargon/lz77.html
https://github.com/DigitalMars/sargon/blob/master/src/sargon/lz77.d
lz77 took 176 hnecs uncompressing
lz4 took 92 hnecs
On Thursday, 28 April 2016 at 17:29:05 UTC, Dmitry Olshansky
wrote:
Compression on the other hand might be helpful to avoid
precompressing everything beforehand.
I fear that is going to be pretty slow and will eat at least 1.5
the memory of the file you are trying to store.
If you want a
On Thursday, 28 April 2016 at 18:31:25 UTC, deadalnix wrote:
Also, the damn thing is allocation in a loop.
I would like a have an allocation primitive for ctfe use.
But that would not help too much as I don't know the size I need
in advance.
storing that in the header is optional, and
On 28-Apr-2016 21:31, deadalnix wrote:
On Thursday, 28 April 2016 at 17:58:50 UTC, Stefan Koch wrote:
On Thursday, 28 April 2016 at 17:29:05 UTC, Dmitry Olshansky wrote:
What's the benefit? I mean after CTFE-decompression they are going to
add weight to the binary as much as decompressed
On Thursday, 28 April 2016 at 17:58:50 UTC, Stefan Koch wrote:
On Thursday, 28 April 2016 at 17:29:05 UTC, Dmitry Olshansky
wrote:
What's the benefit? I mean after CTFE-decompression they are
going to add weight to the binary as much as decompressed
files.
Compression on the other hand
On Thursday, 28 April 2016 at 06:03:46 UTC, Marco Leise wrote:
There exist some comparisons for the C++ implementations
(zlib's DEFLATE being a variation of lz77):
http://catchchallenger.first-world.info//wiki/Quick_Benchmark:_Gzip_vs_Bzip2_vs_LZMA_vs_XZ_vs_LZ4_vs_LZO
Am Tue, 26 Apr 2016 23:55:46 -0700
schrieb Walter Bright :
> On 4/26/2016 3:05 PM, Stefan Koch wrote:
> > Hello,
> >
> > originally I want to wait with this announcement until DConf.
> > But since I working on another toy. I can release this info early.
> >
> > So as
On Wednesday, 27 April 2016 at 07:51:30 UTC, Dejan Lekic wrote:
That is brilliant! I need LZ4 compression for a small project I
work on...
The decompressor is ready to be released.
It should work for all files compressed with the vanilla
lz4c -9
please regard this release as alpha quality.
On Tuesday, 26 April 2016 at 22:05:39 UTC, Stefan Koch wrote:
Hello,
originally I want to wait with this announcement until DConf.
But since I working on another toy. I can release this info
early.
So as per title. you can decompress .lz4 flies created by the
standard lz4hc commnadline tool
On 4/26/2016 3:05 PM, Stefan Koch wrote:
Hello,
originally I want to wait with this announcement until DConf.
But since I working on another toy. I can release this info early.
So as per title. you can decompress .lz4 flies created by the standard lz4hc
commnadline tool at compile time.
No
On Tuesday, 26 April 2016 at 22:07:47 UTC, MrSmith wrote:
I would like to use this instead of c++ static lib. Thanks! (I
hope it works at runtime too).
Oh and If you could please send me a sample of a file you are
trying to uncompress. That would be most helpful.
On Tuesday, 26 April 2016 at 22:07:47 UTC, MrSmith wrote:
I would like to use this instead of c++ static lib. Thanks! (I
hope it works at runtime too).
Sure it does, but keep in mind the c++ version is heavily
optimized.
I would have to make a special runtime version to archive
comparable
On Tuesday, 26 April 2016 at 22:05:39 UTC, Stefan Koch wrote:
Hello,
originally I want to wait with this announcement until DConf.
But since I working on another toy. I can release this info
early.
So as per title. you can decompress .lz4 flies created by the
standard lz4hc commnadline tool
14 matches
Mail list logo