Use custom atoi implementations in the C extractor, so hopefully it does not segfault anymore.
The implementations are tailored for this specific use case and are not generalized for other scenarios, e.g. they do not check for string correctness or overflow. I implemented them like that for simplicity reasons, and for marginally, probably unnoticeably, better performance.
This PR also fixes a typo in database.txt where an "x" was missing from an address (in the "0x"), which is needed for the C extractor to work. Since the database is not expected to suffer any more significant changes, it shouldn't be an issue that the extractor presents certain limitations, and only works with the specific format we are using in the database.
This PR also modifies the README to use the C extractor and not the C# extractor. Beware.
Use custom atoi implementations in the C extractor, so hopefully it does not segfault anymore.
The implementations are tailored for this specific use case and are not generalized for other scenarios, e.g. they do not check for string correctness or overflow. I implemented them like that for simplicity reasons, and for marginally, probably unnoticeably, better performance.
This PR also fixes a typo in
database.txtwhere an "x" was missing from an address (in the "0x"), which is needed for the C extractor to work. Since the database is not expected to suffer any more significant changes, it shouldn't be an issue that the extractor presents certain limitations, and only works with the specific format we are using in the database.This PR also modifies the README to use the C extractor and not the C# extractor. Beware.