Fix

and deprecate LZ4_decompress_fast(),
with deprecation warnings enabled by default.

Note that, as a consequence of the fix,
LZ4_decompress_fast is now __slower__ than LZ4_decompress_safe().
That's because, since it doesn't know the input buffer size,
it must progress more cautiously into the input buffer
to ensure to out-of-bound read.

was disabled for tests

the program exit(),
so there is no need to track and dealloc every buffer.

Fix out-of-bound read in LZ4_decompress_fast()

and created target cxx17build

fix minor Visual warnings

fixed read-after input in LZ4_decompress_safe()

fix #679, reported by @degski

lz4frame: initializers compatibility with C++

to v1.9.1

…!= stdin

This behavior has been preserved for compatibility with existing ecosystem.
But it's problematic, as some environment start `lz4` without identifying stdout as console by default,
leading to a change of behavior for a same line of script.

A more sensible policy would be to default to stdout only when input is stdin.

Soft change for the time being : keep the behavior, just print a warning message.
User should prefer `-c` to explicitly select `stdout`.

Also : updated tests in Makefile to explicitly select `stdout` with `-c`.

for potential redirection, if need be.

note : should probably converge all comparison operations onto CMP

ensure this case is continuously tested on travis.

Update documentation on implicit output,
invite to not rely on implicit output in scripts.

cli: warning for stdout as default output

Implement --list

re-structure code, have everything into a single section of lz4io.c

…nstall" in one place to try to isolate it.

better handling of special conditions,
better scoping of variables.

Also : updated man page

Jpm makefile - as described in #688

strange, because it previous implementation, it would `exit()`,
so it should not matter ...

--list

Moved a few other tests to Makefiles.inc.  Other things might need to go there.
Made a test for symlink appropriateness.  Windows can NOT handle them the same way Unix-like operating systems do (if at all).  This is mostly the same as the Visual C projects.
embed version info into .dll and .exes that are redistributed.

More build imrpvements