[fpc-devel] missed ddk window hints

Hello, FPC developers' list Please apply this patch and merge into fixes if possible. Best regards, Paul Ishenin. Index: packages/gtk2/src/gtk+/gdk/gdkwindow.inc === --- packages/gtk2/src/gtk+/gdk/gdkwindow.inc(revision 11521)

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety, fcl-xml(DOM) is also concerned.

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

Re: [fpc-devel] missed ddk window hints

On Thu, 7 Aug 2008, Paul Ishenin wrote: Hello, FPC developers' list Please apply this patch and merge into fixes if possible. Patched and merged. It's not in 2.2.2, though. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org

Re: [fpc-devel] missed ddk window hints

Michael Van Canneyt wrote: On Thu, 7 Aug 2008, Paul Ishenin wrote: Hello, FPC developers' list Please apply this patch and merge into fixes if possible. Patched and merged. It's not in 2.2.2, though. Thanks. Best regards, Paul Ishenin.

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety, fcl-xml(DOM) is also concerned.

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

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety, fcl-xml(DOM) is also concerned.

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

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety, fcl-xml(DOM) is also concerned.

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

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety, fcl-xml(DOM) is also concerned.

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

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety : second proposition

2008/8/7 Micha Nelissen [EMAIL PROTECTED]: Inoussa OUEDRAOGO wrote: - TAVLManagedTree that uses a node mem manager provided in the constructor. The developer using this one is _aware_ of the thread safety issue and can then provide a thread safe node mem manager for an instance exposed

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety : second proposition

On Thu, 07 Aug 2008 18:04:32 +0200 Micha Nelissen [EMAIL PROTECTED] wrote: Inoussa OUEDRAOGO wrote: - TAVLManagedTree that uses a node mem manager provided in the constructor. The developer using this one is _aware_ of the thread safety issue and can then provide a thread safe node mem

Re: [fpc-devel] TAVLTree(avl_tree.pp) thread safety : second proposition

Inoussa OUEDRAOGO wrote: - TAVLManagedTree that uses a node mem manager provided in the constructor. The developer using this one is _aware_ of the thread safety issue and can then provide a thread safe node mem manager for an instance exposed What is exactly the add-on value