Ichthyostega
56bf5ecc8e
This was a tough nut to crack, but recalling the actual usage situation was helpful * the ''constructor type'' must be created / picked-up beforehand * we are about to build a ''parameter-computation node'' * so this constructor presumably is passed to a type parameter of a specific weaving pattern * the constructor must be invoked directly to drop-off the new data frame into the local scope * it is preferable to attach it only in a second step to the existing HeteroData-Chain (residing in `TurnoutSystem`) What would be ''desirable'' though is to have some additional safeguard in the type system to prevent attaching the newly constructed block to a chain with a non-fitting layout, i.e. the case when several constructors or types get mixed up (because without any further safe-guard this would lead to uncoordinated out-of-bounds memory access) |
||
|---|---|---|
| .. | ||
| basics | ||
| core | ||
| include | ||
| library | ||
| operation | ||
| plugin | ||
| stage | ||
| tool | ||
| vault | ||
| 00helloworld.tests | ||
| 00support.tests | ||
| 00test.tests | ||
| 10errorhandling.tests | ||
| 10exception.tests | ||
| 11concurrency.tests | ||
| 11list.tests | ||
| 11locking.tests | ||
| 11luid.tests | ||
| 11safeclib.tests | ||
| 11time.tests | ||
| 11vault-memory.tests | ||
| 12metaprogramming.tests | ||
| 15library.tests | ||
| 16calculation.tests | ||
| 20config_lowlevel.tests | ||
| 20threads.tests | ||
| 22config_highlevel.tests | ||
| 25fundamental.tests | ||
| 30backend-file.tests | ||
| 30interfaces.tests | ||
| 31plugin.tests | ||
| 32scheduler.tests | ||
| 40core.tests | ||
| 41asset.tests | ||
| 42query.tests | ||
| 43session.tests | ||
| 44controller.tests | ||
| 45builder.tests | ||
| 46fixture.tests | ||
| 46node.tests | ||
| 47engine.tests | ||
| 48playout.tests | ||
| 49core-integration.tests | ||
| 51-gui-model.tests | ||
| 52-gui-control.tests | ||
| 80-regression.tests | ||
| DIR_INFO | ||
| SConscript | ||
| test.conf | ||
| test.sh | ||
| testrunner.cpp | ||