Can someone explain why cascading cuts are done during deleteArbitrary and reweightNode operations? I'm sure there is a good reason and I'd like to understand it.
Printable View
Can someone explain why cascading cuts are done during deleteArbitrary and reweightNode operations? I'm sure there is a good reason and I'd like to understand it.
And many still wonder why Captain Picard failed to understand the threat of the Borg right?Quote:
Originally Posted by ClaytonWohl
Just kidding but maybe you should explain your problem a little bit better.
What's a 'delereArbitrary' operation? What's a 'reweightNode' operation?
Viggy
"deleteArbitrary" is when you delete an arbitrary node from the heap. reweightNode is when you change the weight (or ordering value) of an existing heap node.
I take it that you don't know the answer to my question.
As nuzzle alluded to, you need to be a little more specific. These functions are not in any standard library I've had to work with. They are not part of the standard C/C++ library:
Also, a "heap", for client (i.e. programmer) use is not standard as well.Code:> man deleteArbitrary
No manual entry for deleteArbitrary
...
> man reweightNode
No manual entry for reweightNode
Viggy