Difference between revisions of "Documentation/DevGuide/ProUNO/CLI/Type Name Decoration"
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Professional UNO) |
OOoWikiBot (Talk | contribs) m (FINAL VERSION FOR L10N) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
|NextPage=Documentation/DevGuide/ProUNO/CLI/Type Mappings | |NextPage=Documentation/DevGuide/ProUNO/CLI/Type Mappings | ||
}} | }} | ||
| + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/ProUNO/CLI/{{SUBPAGENAME}}}} | ||
{{DISPLAYTITLE:Type Name Decoration}} | {{DISPLAYTITLE:Type Name Decoration}} | ||
IDL type names can potentially conflict with type names of a particular language, or a name from one language could also be used in another language. In these cases, interactions between those language environments are prone to errors, because types are misinterpreted and incorrectly handled. To counter the problem, the bridge decorates all imported and exported type names. For example, the type <code>a.b.c</code> is transferred from one environment into a .NET environment. Then the bridge prefixes the name with a string, so that the name is <code>unoidl.a.b.c</code> When that type is sent back into the environment where it came from, then the bridge removes the "<code>unoidl.</code>" prefix. Likewise, if a type that was defined in the CLI environment is transferred out of that environment, the name is prefixed with "<code>cli.</code>" On return, the prefix will be removed again. For more information, see the concept paper ''Names in UNO''. It can be found at: [http://udk.openoffice.org/common/man/names.html http://udk.openoffice.org/common/man/names.html ]. | IDL type names can potentially conflict with type names of a particular language, or a name from one language could also be used in another language. In these cases, interactions between those language environments are prone to errors, because types are misinterpreted and incorrectly handled. To counter the problem, the bridge decorates all imported and exported type names. For example, the type <code>a.b.c</code> is transferred from one environment into a .NET environment. Then the bridge prefixes the name with a string, so that the name is <code>unoidl.a.b.c</code> When that type is sent back into the environment where it came from, then the bridge removes the "<code>unoidl.</code>" prefix. Likewise, if a type that was defined in the CLI environment is transferred out of that environment, the name is prefixed with "<code>cli.</code>" On return, the prefix will be removed again. For more information, see the concept paper ''Names in UNO''. It can be found at: [http://udk.openoffice.org/common/man/names.html http://udk.openoffice.org/common/man/names.html ]. | ||
| Line 14: | Line 15: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category:Documentation/ | + | [[Category:Documentation/Developer's Guide/Professional UNO]] |
Revision as of 08:25, 13 May 2009
IDL type names can potentially conflict with type names of a particular language, or a name from one language could also be used in another language. In these cases, interactions between those language environments are prone to errors, because types are misinterpreted and incorrectly handled. To counter the problem, the bridge decorates all imported and exported type names. For example, the type a.b.c is transferred from one environment into a .NET environment. Then the bridge prefixes the name with a string, so that the name is unoidl.a.b.c When that type is sent back into the environment where it came from, then the bridge removes the "unoidl." prefix. Likewise, if a type that was defined in the CLI environment is transferred out of that environment, the name is prefixed with "cli." On return, the prefix will be removed again. For more information, see the concept paper Names in UNO. It can be found at: http://udk.openoffice.org/common/man/names.html .
When CLI types are declared, their names must not start with "unoidl." And types declared in UNOIDL must not start with "cli."
| Content on this page is licensed under the Public Documentation License (PDL). |
