Free cookie consent management tool by TermsFeed Policy Generator
wiki:ModularizationAndReuseWithOperatorLibraries

Version 1 (modified by gkronber, 16 years ago) (diff)

created a page about modularization and reuse with description and the main limitation

Modularization and Reuse

Operator-libraries in HL3 are a powerful mechanism to enable reuse and modularization of operator-trees. In combination with the abstraction mechanism provided by CombinedOperators and OperatorExtractors it is very easy to define high-level building-blocks by encapsulating operator-trees. These building blocks can be stored into an operator-library and later be reused in other engines that also need the functionality provided by the collection of building-blocks.

Limitations

Even though HL3 has OperatorLibraries for modularization and CombinedOperators for abstraction there is a limiting factor that restricts reuse of operator-trees (also see #107). The problem is that using an operator from the library means copying the definition into the executable operator-tree. This means that when the definition of an operator in a module changes is also has to be manually changed in all existing operator-graphs that contain copies of that operator. Instead of 'code-reuse' what actually happens is 'code-duplication'.

Ideas

Using-Operator