32
edits
Memory Management for nsIScriptContext: Difference between revisions
Memory Management for nsIScriptContext (view source)
Revision as of 07:08, 14 September 2005
, 14 September 2005Mention XULElement::GetCompiledEventHandler() copies the void *
(added an alternative to the first binding option) |
(Mention XULElement::GetCompiledEventHandler() copies the void *) |
||
| Line 51: | Line 51: | ||
* All such objects returned by nsIScriptContext are considered "locked". They must remain locked while they are held externally. An 'unlock' function will be provided by the language to unlock the object. | * All such objects returned by nsIScriptContext are considered "locked". They must remain locked while they are held externally. An 'unlock' function will be provided by the language to unlock the object. | ||
* It is likely that users of this interface may need to copy the returned object and manage the lifetimes seperately (for example, storing the returned "void *" in 2 unrelated datastructures). For this scenario, an explicit "lock()" call will be provided (meaning 2 unlock calls are now needed to finalize the object). However, as mentioned above, objects will always be returned locked so calling this will be rare. ( | * It is likely that users of this interface may need to copy the returned object and manage the lifetimes seperately (for example, storing the returned "void *" in 2 unrelated datastructures). For this scenario, an explicit "lock()" call will be provided (meaning 2 unlock calls are now needed to finalize the object). However, as mentioned above, objects will always be returned locked so calling this will be rare. XULElement::GetCompiledEventHandler() is the only identified place that does this. | ||
===Bound Event Handlers=== | ===Bound Event Handlers=== | ||