Changed algorithm to speed up fixSingleBitErrors() and fixTwoBitsErrors().

[Kalofin]

Old: Modify a single or two bits in a message, recalculate CRC, start over until a CRC error free message is found. New: Calculate CRC, identify incorrect message bits, correct message.

• The new approach does not need to recalculate the CRC of the whole message for each iteration. Allows fixing of two bit errors on "slow" systems like RaspberryPi.
• DF11 and DF17 messages are subjected to TwoBitErrorCorrection if '--aggressive' is used.

[antirez]

Hello, thanks for your contrib, looks interesting, I'll review the next time I get some free time.

This fork is still maintained but with time limits, and still targets codebase minimalism, so I linked in the README that there is the MalcolmRobb fork available for users demanding more features and a more active development.

[antirez]

p.s. it would be nice if @MalcolmRobb will do the same and modify the README to write that the code originates from this project (not for lack of credits, in the current README there is only my name!) and what are the goals of the fork. It's great that there is a fork with a lot of features (I use it myself from time to time) but for the user base it is clear if we cross-reference the two forks with explanation about differences.

[MalcolmRobb]

Antirez - I'm happy to update 'my' read me, but I don't know how to update the copyright/license. This has worried me for some time. I've left all you original headers in all the files, but I would like to know how to include credits to other contributors without violating your licence. I'm also not sure whether your license is correct. Your readme says it's released under a 3 clause BSD licence, but most of the files only contain 2 clauses in the header.

Cheers Malcolm