C++'s destructors can be destructive

A comparison of Ada and C++

“…Since the destructor is called automatically, the user may not know that the internal structures of an object have been unexpectedly destroyed. The result is disastrous and difficult to debug [14]. As an example, consider a class A that contains a pointer P and a destructor for releasing the space pointed to by P, This may be surprising for beginner C++ programmers.…”

40.3L: Late‐News Paper: Color Changing Materials for OLED Microdisplays

“…There are several approaches to color OLED displays, among them: pixels emitting blue light with fluorescing color changing media (CCM) on top of them [1]; pixels emitting white light with color filters on top of them [2]; and self-emissive pixelated display with RGB pixels placed next to each other [3]. In principle, the latter approach allows the best possible performance because no light is lost for filter absorption or color conversion.…”

Passing large dynamic objects out of function frame boundaries

“…Secondly, if instead the object is created in heap memory (free store) and a reference is returned, the problem of how the memory occupied by such an object ever get reclaimed arises. This is a 'memory leak' situation [1] [2].…”