Inoussa OUEDRAOGO wrote:
2008/8/6 Micha Nelissen [EMAIL PROTECTED]:
Perhaps another option is to remove the NodeMemManager altogether and
simply use GetMem/FreeMem (or New/Dispose)?
The second proposition contains a default TAVLTree that remove the node
mem manager and TAVLManagedTree that
Am Mittwoch, 6. August 2008 21:37 schrieb Sergei Gorelkin:
Mattias Gaertner wrote:
On Wed, 6 Aug 2008 19:41:27 +0100
Inoussa OUEDRAOGO [EMAIL PROTECTED] wrote:
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
Zitat von Burkhard Carstens [EMAIL PROTECTED]:
Am Mittwoch, 6. August 2008 21:37 schrieb Sergei Gorelkin:
Since this topic is touched, I would like to vote for removing
avl_tree dependency from the DOM altogether. The reason is that the
avl tree of child nodes is useless for any real-world
Am Mittwoch, 6. August 2008 20:41 schrieb Inoussa OUEDRAOGO:
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is cleary not thread safe, which btw IMHO
Am Mittwoch, 6. August 2008 20:41 schrieb Inoussa OUEDRAOGO:
What about this:
* let TAVLTree access the node manager using a local reference
(TAVLTree.FNodeMemManager)
* in TAVLTree.create:
if IsMultiThread then
FNodeMemManager:=TAVLTreeNodeMemManager.create
else
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is cleary not thread safe, which btw IMHO
is a good thing ( for performance reason).
Proposition :
(a)
On Wed, 6 Aug 2008 19:41:27 +0100
Inoussa OUEDRAOGO [EMAIL PROTECTED] wrote:
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is cleary not thread
Inoussa OUEDRAOGO wrote:
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is cleary not thread safe, which btw IMHO
is a good thing ( for performance reason).
Mattias Gaertner wrote:
On Wed, 6 Aug 2008 19:41:27 +0100
Inoussa OUEDRAOGO [EMAIL PROTECTED] wrote:
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is
2008/8/6 Micha Nelissen [EMAIL PROTECTED]:
Inoussa OUEDRAOGO wrote:
Hi,
TAVLTree in avl_tree.pp is not thread safe due to the node
allocation and de-allocation done through the global
declared NodeMemManager variable. TAVLTreeNodeMemManager
implementation is cleary not thread safe, which
10 matches
Mail list logo