Node constructor. A universe size provided, if the size is below the cutoff there is nothing to be done, as the
underlying value created and set to zero by default.
If otherwise create an array of children. This array has to be (according to Cormen) of size of higher square
root of the current universe size + 1. The extra place is reserved for the summary.
For each just created child call its constructor.
For the summary with the universe size of the higher square root of the current universe size.
For each other child with the universe size of the lower square root of the currennt universe size.
Then, assign the fully initialized children array to the pointer in the current node, doing approprate steps to
show, that this node is an intermediate node, not containing any values yet.
The knowledge of the current universe size is lost at this moment. As this keeps every build up node smaller
(and there could be a lot of them). This is why, the VEBtree class continues to hold the global universe size,
which is passed on every call to the root node. In this way this, extern saved value has the role of being
outsourced array size for each (!) node in the tree, as its size is reconstructed during the access to them.
Node constructor. A universe size provided, if the size is below the cutoff there is nothing to be done, as the underlying value created and set to zero by default. If otherwise create an array of children. This array has to be (according to Cormen) of size of higher square root of the current universe size + 1. The extra place is reserved for the summary. For each just created child call its constructor. For the summary with the universe size of the higher square root of the current universe size. For each other child with the universe size of the lower square root of the currennt universe size. Then, assign the fully initialized children array to the pointer in the current node, doing approprate steps to show, that this node is an intermediate node, not containing any values yet. The knowledge of the current universe size is lost at this moment. As this keeps every build up node smaller (and there could be a lot of them). This is why, the VEBtree class continues to hold the global universe size, which is passed on every call to the root node. In this way this, extern saved value has the role of being outsourced array size for each (!) node in the tree, as its size is reconstructed during the access to them.