Difference between revisions of "Documentation/DevGuide/ProUNO/Lifetime of UNO objects"
From Apache OpenOffice Wiki
< Documentation | DevGuide
m (1 revision(s)) |
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Professional UNO) |
||
| Line 15: | Line 15: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category: Professional UNO]] | + | |
| + | [[Category:Documentation/Developers Guide/Professional UNO]] | ||
Revision as of 15:15, 8 May 2008
The UNO component model has a strong impact on the lifetime of UNO objects, in contrast to CORBA, where object lifetime is completely unspecified. UNO uses the same mechanism as Microsoft COM by handling the lifetime of objects by reference counting.
Each UNO runtime environment defines its own specification on lifetime management. While in C++ UNO, each object maintains its own reference count. Java UNO uses the normal Java garbage collector mechanism. The UNO core of each runtime environment needs to ensure that it upholds the semantics of reference counting towards other UNO environments.
The last paragraph of this chapter explains the differences between the lifetime of Java and C++ objects in detail.
| Content on this page is licensed under the Public Documentation License (PDL). |
