kevacoin

232 Tags

129 MiB

Tree: 638a5a715c

Author	SHA1	Message	Date
isle2983	27765b6403	Increment MIT Licence copyright header year on files modified in 2016 Edited via: $ contrib/devtools/copyright_header.py update .	8 years ago
Pavel Janík	4731cab8fb	Do not shadow variables	8 years ago
Cory Fields	89f71c68c0	c++11: don't throw from the reverselock destructor noexcept is default for destructors as of c++11. By throwing in reverselock's destructor if it's lock has been tampered with, the likely result is std::terminate being called. Indeed that happened before this change. Once reverselock has taken another lock (its ctor didn't throw), it makes no sense to try to grab or lock the parent lock. That is be broken/undefined behavior depending on the parent lock's implementation, but it shouldn't cause the reverselock to fail to re-lock when destroyed. To avoid those problems, simply swap the parent lock's contents with a dummy for the duration of the lock. That will ensure that any undefined behavior is caught at the call-site rather than the reverse lock's destruction. Barring a failed mutex unlock which would be indicative of a larger problem, the destructor should now never throw.	9 years ago
Casey Rodarmor	86270c8164	Replace boost::reverse_lock with our own.	9 years ago