Ichthyostega
75c0d66b91
Overall, this is a questionable endeavour... - I want a framework that can be extended flexibly - I am concerned about the performance penalty of that flexibility What makes this situation problematic is the fact that I am deep in prototyping work here, and have not the slightest idea as to what would be the actual usage context. So I am lacking a point of reference, yet still I am engaged into a very tricky (premature) optimisation... Anyway. I have now found a way to integrate an optimised access code-path in a safe way, while retaining the general case with flexible type conversion: - whenever a BaseDomain<X> is used, a corresponding type-ID is marked into the ID-Record - this allows when it is possible to side-step any type conversion, - in which case we can also forcibly side-step the virtual dispatch, and invoke directly the value-accessors of the default implementation, reaching into the embedded value buffer. |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||
| Workflow_Verwijlen.mm | ||