Steeve Morin

@arnefm your log doesn't show anything wrong

Nice catch ! I think we should check out what is LZ4's fault, and what is the binding's (aka my) fault... Because I'm not in favor of patching lz4.c (which...

Although checking `lz4.h`, all the size are handled as `int`, so I guess LZ4 should work on that too...

Why not force `int64_t`? After all, even on 32 bits systems, having stuff over 2gb could be possible (with PAE), although unlikely....

For the record, @Cyan4973 is Yann Collet :)

Going on old issues. Is this one fixed? I'm gonna update the release this week.

Hey Yann, Thanks for the heads up. Is the format spec implemented in `lz4.c`? In which case I'll find some time to update it.

Where is this file? I don't see it in https://code.google.com/p/lz4/source/browse/#svn%2Ftrunk

Definitely. The simpler it is to wrap, the better :) On Mon, Jan 13, 2014 at 11:55 PM, Cyan4973 [email protected] wrote: > Would that help if functions to create compressed...

The issue is, what about stream? Basically python's lz4 takes a string as input, and outputs a string with the data. Is there a way for it to use `char*`...