Author: Ron 2014-06-04 19:13:45
Published on: 2014-06-04T19:13:45+00:00
In this email, Jeff Garzik responds to a previous message about the error "Bitcoin cannot be compiled without assertions." Garzik suggests that check macros can be useful and he likes the kernel's policy of enabling and using lightweight assertions for most users. He also mentions that no assertions with side effects should be present in production software. Garzik clarifies that he intentionally left the gcc code alone and only the MSC code is assert fixed. He provides an example from main.cpp CTransaction::UpdateCoins() and explains how he changed every assert() in the bitcoind 086 sources to behave in a certain way. He argues his "fix" is better than the one used in version 0.9.x since it allows release mode code to run better. Garzik also links to a resource on consistency checking and asks whether bitcoin-qt should be compiled in release or debug mode.
Updated on: 2023-06-08T23:40:46.364351+00:00