Tree:
bc909a7a7f
dev
master
0.9.4
v.0.4.0f
v0.11.2.z0
v0.11.2.z1
v0.11.2.z2
v0.11.2.z3
v0.11.2.z4
v0.11.2.z5
v0.11.2.z6
v0.11.2.z7
v0.11.2.z8
v0.11.2.z9
v0.2.36-beta
v0.3.10-beta
v0.3.11-beta
v0.3.12-beta
v0.3.12a-beta
v0.3.13-beta
v0.3.3-beta
v0.4.0
v0.4.0a
v0.4.0b
v0.4.0c
v0.4.0e
v0.4.0f
v0.4.0g
v0.4.0h
v0.5.0
v0.5.1
v0.5.3
v0.5.4
v0.5.5
v0.5.5b
v0.5.5c
v0.5.6
v0.5.6a
v0.5.7
v0.5.7-1
v0.5.7-2
v0.5.8
v0.5.9
v0.5.9-1
v0.5.9-2
v0.5.9-22
v0.5.9-24
v0.5.9-37
v0.5.9-38
v0.5.9-42
v0.6.0
v0.6.0-1
v0.6.0-2
v0.6.0-3
v0.6.0-4
v0.6.0-5
v0.6.0-6
v0.6.0-7
v0.6.0-8
v0.6.0-PBaaS-Cross-chain-Technology-Preview
v0.6.0-tech-preview-01
v0.6.0-tech-preview-02
v0.6.0.12-PBaaS-Cross-chain-Technology-Preview
v0.6.0.24-PBaaS-Cross-chain-Technology-Preview
v0.6.0.28-PBaaS-Cross-chain-Technology-Preview
v0.6.0.29-PBaaS-Cross-chain-Technology-Preview
v0.6.0.33-PBaaS-Cross-chain-Technology-Preview
v0.6.0.34-PBaaS-Cross-chain-Technology-Preview
v0.6.0.7-PBaaS-Cross-chain-Technology-Preview
v0.6.0.9-PBaaS-Cross-chain-Technology-Preview
v0.6.1
v0.6.2
v0.6.2-1
v0.6.4
v0.6.4-1
v0.6.4-3
v0.6.5
v0.6.5-1
v0.6.5-2
v0.7.0
v0.7.0-1
v0.7.0-3
v0.7.0-4
v0.7.1
v0.7.1-1
v0.7.1-2
v0.7.1-3
v0.7.1-4
v0.7.1-5
v0.7.2
v0.7.2-1
v0.7.2-2
v0.7.2-3
v0.7.2-4
v0.7.2-5
v0.7.2-6
v0.7.2-7
v0.7.2-8
v0.7.3
v0.7.3-1
v0.7.3-10
v0.7.3-2
v0.7.3-3
v0.7.3-4
v0.7.3-5
v0.7.3-6
v0.7.3-7
v0.7.3-8
v0.7.3-9
v0.7.4
v0.8.0
v0.8.0-1
v0.8.0-2
v0.8.0-3
v0.8.0-4
v0.8.0-5
v0.9.0
v0.9.0-1
v0.9.0-2
v0.9.0-3
v0.9.1
v0.9.1-1
v0.9.1-2
v0.9.2
v0.9.2-1
v0.9.2-2
v0.9.2-3
v0.9.3
v0.9.4
v0.9.4-1
v0.9.4-2
v0.9.4-3
v0.9.4-4
v0.9.4-5
v1.0.0-beta1
${ noResults }
3 Commits (bc909a7a7f0553d8ec80fa6c36a4faf8609edcf7)
Author | SHA1 | Message | Date |
---|---|---|---|
Daira Hopwood | bc909a7a7f |
Replace http with https: in links to the MIT license.
Also change MIT/X11 to just MIT, since no distinction was intended. Signed-off-by: Daira Hopwood <daira@jacaranda.org> |
5 years ago |
Cory Fields |
4165af1b73
|
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 | 6b51b9b195 |
Replace boost::reverse_lock with our own.
|
9 years ago |