LUMIERA.clone/research
Ichthyostega eebe31aa7e DI: change to heap allocation for singletons
up to now we used placement into a static buffer.
While this approach is somewhat cool, I can't see much practical benefit anymore,
given that we use an elaborate framework which rules out the use of Meyers Singleton.
And given that with C++11 we're able just to use std::unique_ptr to do all work.

Moreover, the intended configurability will become much simpler by relying
on a _closure_ to produce a heap-allocated instance for all cases likewise.

The only possible problem I can see is that critical infrastructure might
rely on failsafe creation of some singleton. Up to now this scenario
remains theoretical however
2018-03-17 23:41:56 +01:00
..
clang-static-init-1.cpp BUG: Clang shows a problem when accessing templated static variable through separate compilation units 2013-10-06 23:17:18 +02:00
clang-static-init-2.cpp bughunt: re-create the whole 2nd layer with a configurable product type --> HIT 2013-10-06 23:17:18 +02:00
clang-static-init.hpp BUG: Clang shows a problem when accessing templated static variable through separate compilation units 2013-10-06 23:17:18 +02:00
crash_gdb_jessie-2015-08.sh investigation: Segfault in GDB (IV) (related to #946) 2015-08-16 01:17:35 +02:00
DIR_INFO SCons: new build target for experimental code 2011-12-03 06:10:12 +01:00
SConscript experiment: now bind a Proc-Layer command to these fabricated functions 2016-01-15 23:55:44 +01:00
try.cpp DI: change to heap allocation for singletons 2018-03-17 23:41:56 +01:00