Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Gathers are inherently expensive and are best used either
1. Near the beginning/end of execution to amortize costs across an entire run or
2. Temporarily while developing/debugging code.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.