Difference between revisions of "Documentation/DevGuide/ProUNO/UNO Language Bindings"
From Apache OpenOffice Wiki
< Documentation | DevGuide
m (1 revision(s)) |
OOoWikiBot (Talk | contribs) m (FINAL VERSION FOR L10N) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
|NextPage=Documentation/DevGuide/ProUNO/Java/Java Language Binding | |NextPage=Documentation/DevGuide/ProUNO/Java/Java Language Binding | ||
}} | }} | ||
| + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/ProUNO/{{SUBPAGENAME}}}} | ||
{{DISPLAYTITLE:UNO Language Bindings}} | {{DISPLAYTITLE:UNO Language Bindings}} | ||
This chapter documents the mapping of UNO to various programming languages or component models. This language binding is sometimes called a UNO Runtime Environment (URE). Each URE needs to fulfill the specifications given in the earlier chapters. The use of UNO services and interfaces are also explained in this chapter. Refer to [[Documentation/DevGuide/WritingUNO/Writing UNO Components|Writing UNO Components]] for information about the implementation of UNO objects. | This chapter documents the mapping of UNO to various programming languages or component models. This language binding is sometimes called a UNO Runtime Environment (URE). Each URE needs to fulfill the specifications given in the earlier chapters. The use of UNO services and interfaces are also explained in this chapter. Refer to [[Documentation/DevGuide/WritingUNO/Writing UNO Components|Writing UNO Components]] for information about the implementation of UNO objects. | ||
| Line 18: | Line 19: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category: Professional UNO]] | + | |
| + | [[Category:Documentation/Developer's Guide/Professional UNO]] | ||
Revision as of 08:00, 13 May 2009
This chapter documents the mapping of UNO to various programming languages or component models. This language binding is sometimes called a UNO Runtime Environment (URE). Each URE needs to fulfill the specifications given in the earlier chapters. The use of UNO services and interfaces are also explained in this chapter. Refer to Writing UNO Components for information about the implementation of UNO objects.
Each section provides detail information for the following topics:
- Mapping of all UNO types to the programming language types.
- Mapping of the UNO exception handling to the programming language.
- Mapping of the fundamental object features (querying interfaces, object lifetime, object identity).
- Bootstrapping of a service manager.Other programming language specific material (like core libraries in C++ UNO).
Java, C++, OpenOffice.org Basic, and all languages supporting MS OLE automation or the Common Language Infrastructure (CLI) on the win32 platform are currently supported. In the future, the number of supported language bindings may be extended.
| Content on this page is licensed under the Public Documentation License (PDL). |
