David Steele ef4c4ab852 Use variable instead of function to track FINALLY() state. ... The function worked fine, but Coverity was unable to determine that the finally block was run, which led to false positives about unfreed memory. Using a boolean in the block makes it clear to Coverity that the finally block will always be run no matter what else happens. We'll depend on the compiler to optimize away the boolean if it is not used in a finally block. The cost of the boolean is fairly low in comparison to everything else being done in these macros, so it does not seem worth having a separate block even if the compiler is not able to eliminate the boolean. This reverts most of 9a271e9 that fixed a bug caused by c5b5b58, which was also attempting to help Coverity understand FINALLY() blocks.		2022-05-09 10:39:43 -04:00
..
auto	v2.38: Minor Bug Fixes and Improvements	2022-03-06 10:30:59 -06:00
dtd	Eliminate linefeed formatting from documentation.	2021-09-08 17:35:45 -04:00
coding.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
contributing.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
documentation.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
faq.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
index.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
metric.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
release.xml	Use variable instead of function to track FINALLY() state.	2022-05-09 10:39:43 -04:00
user-guide-index.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00
user-guide.xml	Clean up dividers in the documentation.	2022-05-06 12:11:04 -04:00