# FeatStd V3.4.2

#### Release Info

<div class="contents" id="bkmrk-release-date%3A-septem"><div class="contents"><div class="textblock">- Release Date: September 2017

</div></div></div>#### Interface Changes

<div class="contents" id="bkmrk-removal-of-log-realm"><div class="contents"><div class="textblock">- Removal of Log Realm limitation
- Extension of Initialized and Optional classes by comparison operator

---

</div></div></div>#### Removal of Log Realm limitation

The name of a log realm were bound to a maximum length of 32 characters including the terminating null byte. This limitation has been removed. Existing logger (appender) are using the CMake macro FEATSTD\_LOGGER\_MAX\_BUFFER\_SIZE now. If the name is still too long and does not fit into the buffers, this CMake flag can be adjusted accordingly. Note that appenders statically reserve these buffers.

<div class="contents" id="bkmrk-"><div class="contents"><div class="textblock">  
</div></div></div>#### Extension of Initialized and Optional classes by comparison operator

The [Initialized](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_initialized.html) and [Optional](http://dev.doc.cgistudio.at/APILINK/class_feat_std_1_1_optional.html "The template class Optional is a wrapper for representing optional objects that may not have been ini...") classes are extended to forward the comparison operators to the underlying value. This includes pointer comparison if the type is a pointer type.

<div class="contents" id="bkmrk--0"><div class="contents"><div class="textblock">  
</div></div></div>#### UnitTest-Helper extended by MemoryLeak check

The unit test helper class 'EnvironmentTestEventListener' includes a memory check after all test cases. The check is done after all subtests of a test (class) are done and the teardown for this test case has been processed. It shows new potential leaks after the test case. This feature is only available if MemoryPools are enabled and memory leak detection for MemoryPools is also enabled.

Important notes: Static preallocations which are available over the complete runtime are marked as memory leaks even if they are cleaned up correctly afterwards. Additionally, unit tests may have no focus on correct clean ups. These memory leaks are also visible.

---