How does DFHTBSBP do its work?

First, you must examine more closely the structure of a builder in Figure 1.
Figure 1. The builder stub
Diagram illustrating the structure of a builder.

Remember that the pattern references a builder. In fact, it references a stub, the first word of which points to a table (BSH_EP_TABLE), and is followed by code that is responsible for enacting the entry as required by the caller. For example, if the caller wanted to call BUILD, a call would be made to the stub with value 1. The stub would extract the offset to the build code from the BSH_EP_TABLE, and perform the call.

Thus, making a call from DFHTBS* to DFHBS* is relatively simple: all that is needed is the function number (1 for BUILD, 2 for DESTROY, ...), a call to the stub, and the pattern.

Summary

  • The TCTTE is structured as a hierarchy with a master node (the TCTTE itself) and subnodes (BIND image, BMS extension, and so on).
  • Patterns mimic this hierarchy and consist of a master pattern which refers to subpatterns.
  • In turn, each pattern points to a builder: the master pattern refers to the master builder and the subpatterns refer to the sub-builders.
  • Builders centralize the major creation and deletion functions associated with the node for which they are responsible.
  • The invocation (or activation) of the builder functions is performed under the strict control of the DFHTBS* modules.
  • The order of invocation is totally determined by the structuring of the patterns.


dfhs3c00127.html | Timestamp icon Last updated: Monday, 5 June 2017