...on top of the parameter-decorating functionality developed thus far. The idea is to allow in the `NodeBuilder` to supply ''some parameters'' directly, while the remaining parameters will be drawn from automation. Several years ago, I developed some helpers for partial function closure. Unfortunately these utils are somewhat limited, and rely on some pre-C++11 constructs, yet seem to be usable for the task at hand, since parameters are always expected as value objects by definition. This changeset shows a working proof-of concept for left-closing a parameter tuple with 5 elements; this turns out to surprisingly difficult due to the full genericity of the acceptable parameter-aggregates... |
||
|---|---|---|
| .. | ||
| 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 | ||