seems that I've played too much with »undefined behaviour« in this test; basically we can not assume ''any'' specific placement of local variables in a stack frame.... In this test, what I wanted to demonstrate is that the overflow-block can reside just »anywhere«, and that HeteraoData is just a light-weight front-End and accessor. However, I can just demonstrate that without totally ''undefined behaviour;'' placement-new can be used to force the storage at a specific location (in the UninitialiesdStorage); continue to access and use that data after leaving the nested scope is still kind-of borderline, yet demonstrates that the data itself is just residing in a storage block... |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||