Ichthyostega 6073df3554 Looper: other (better?) idea how to handle "builder dirty" automatically ... ...this means to turn Looper into a state machine. Yet it seems more feasible, since the DispatcherLoop has a nice checkpoint after each iteration through the while loop, and we'd keep that whole builder-dirty business completely confined within the Looper (with a little help of the DispatcherLoop) Let's see if the state transition logic can actually be implemented based just on such a checkpoint....?		2016-12-20 03:53:48 +01:00
..
application	clean-up: mark subsystem implementations with noexcept and override	2016-12-12 01:18:19 +01:00
backend	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
proc	Looper: other (better?) idea how to handle "builder dirty" automatically	2016-12-20 03:53:48 +01:00
DIR_INFO	re-arrange tests according to layer structure	2013-01-07 05:43:01 +01:00