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) |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||