It has some promise, however: * The code generates a number of warnings when compiled with '-Wall -Wpedantic'. Look at IOCCC entries; a number of them take pr

It has some promise, however: * The code generates a number of warnings when compiled with '-Wall -Wpedantic'. Look at IOCCC entries; a number of them take pride in having no warnings whatsoever, even with full warnings enabled. * The code does not include instructions. Even a 12-line 900 character obfuscated program can include basic usage instructions. * Most importantly, the code does not work. When I compiled it with GCC on Cygwin (gcc -o zolW zolW.c -lncurses), then ran 'touch foo ; ./zolW foo', I almost immediately got a core dump. So, yes, this is a good first attempt, but I would like to see this get revised. Fix all compile time warnings; make sure it works with both GCC and CLANG. Add test cases. Add documentation. Shameless plug: Yes, I have made a small, 900 character 12 line program which does not generate compile-time warnings, does not generate core dumps (even going so far as to fix a core dump which only happened after running the code for over an hour and generating 16 gigabytes of data), has a usage manual, has test cases, and even has basic usage information in the code. So I know it can be done. See https://github.com/samboy/rg32hash/blob/master/C/tinyrg32.md https://github.com/samboy/rg32hash/blob/master/C/tinyrg32.md and scroll down for the actual obfuscated C code.