Difference between revisions of "Uno/Spec/Cascaded Mapping"
From Apache OpenOffice Wiki
m (improved wording; improved layout.) |
m (Added some links.) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Uno/Meta/Organization#Types|Type]]: Specification [[Uno/Meta/Organization#States|State]]: final [[Uno/Meta/Organization#Claims|Claim]]: recommended | |
| − | + | ||
| − | + | ||
| − | + | ==Feature== | |
| − | + | Cascaded mapping generalizes the runtimes search&connect algorithm in a way, that it always finds a mapping between any two particular (purpose) [[Uno/Spec/Environment|environments]], necessarily falling back to the generic [[Uno/Binary/Spec/Uno Environment|Uno Environment]] for mediation, in case no specialized bridges ([[Uno/Spec/Mapping|mappings]]) can be found. | |
| − | + | ||
| − | Cascaded mapping generalizes the | + | |
For example: | For example: | ||
| − | <code>uno::Mapping(" | + | <code>uno::Mapping("C++:unsafe", "C++")</code> |
| − | gets mediated via the "unsafe_uno_uno" purpose bridge: | + | gets mediated via the <code>"unsafe_uno_uno"</code> purpose bridge: |
| − | => Mapping(" | + | => Mapping("C++:unsafe" -> "uno:unsafe" -> "uno" -> "C++") |
| − | + | ==Mapping Algorithm== | |
# In case both environments are of the same purpose, map directly, e.g. <br> "uno:unsafe" -> "gcc3:unsafe" => "uno:unsafe" -gcc3_uno-> "gcc3:unsafe" . | # In case both environments are of the same purpose, map directly, e.g. <br> "uno:unsafe" -> "gcc3:unsafe" => "uno:unsafe" -gcc3_uno-> "gcc3:unsafe" . | ||
# Mediate through a purpose bridge, in case it is asked for a mapping between different purposes, e.g. <br> "uno:unsafe" -unsafe_uno_uno-> "uno", the purpose bridge here is "unsafe_uno_uno". | # Mediate through a purpose bridge, in case it is asked for a mapping between different purposes, e.g. <br> "uno:unsafe" -unsafe_uno_uno-> "uno", the purpose bridge here is "unsafe_uno_uno". | ||
| Line 22: | Line 18: | ||
The mapping algorithm does not know any particular purpose. It is just leverages the current purpose API. | The mapping algorithm does not know any particular purpose. It is just leverages the current purpose API. | ||
| − | + | ==Rationale== | |
| − | The introduction of purpose environments allows to instantiate multiple environments of the same ABI (e.g. "gcc3") but with different purposes. Cascaded mappings allows to map between environments of different purposes, by using the | + | The introduction of purpose environments allows to instantiate multiple environments of the same ABI (e.g. "gcc3") but with different purposes. Cascaded mappings allows to map between environments of different purposes, by using the Uno runtimes purpose mapping mechanism. |
| − | == | + | ==Dependencies== |
| − | + | * [[../Purpose Environment]] | |
| − | |||
| − | |||
| + | [[Category:Spec]] | ||
| + | [[Category:Uno]] | ||
[[Category:Uno:Spec]] | [[Category:Uno:Spec]] | ||
Latest revision as of 09:01, 13 February 2007
Type: Specification State: final Claim: recommended
Feature
Cascaded mapping generalizes the runtimes search&connect algorithm in a way, that it always finds a mapping between any two particular (purpose) environments, necessarily falling back to the generic Uno Environment for mediation, in case no specialized bridges (mappings) can be found.
For example:
uno::Mapping("C++:unsafe", "C++")
gets mediated via the "unsafe_uno_uno" purpose bridge:
=> Mapping("C++:unsafe" -> "uno:unsafe" -> "uno" -> "C++")
Mapping Algorithm
- In case both environments are of the same purpose, map directly, e.g.
"uno:unsafe" -> "gcc3:unsafe" => "uno:unsafe" -gcc3_uno-> "gcc3:unsafe" . - Mediate through a purpose bridge, in case it is asked for a mapping between different purposes, e.g.
"uno:unsafe" -unsafe_uno_uno-> "uno", the purpose bridge here is "unsafe_uno_uno". - Mediate through the "uno" environment, if asked for a mapping from one purpose environment to another purpose environment, e.g.
"uno:unsafe" -> "uno:affine" => "uno:unsafe" -unsafe_uno_uno-> "uno" -affine_uno_uno-> "uno:affine". - Recursively apply -4- in case a multi purpose environment has been specified, e.g.
"gcc3:unsafe:debug" -> "gcc3:affine" => "gcc3:unsafe:debug" -gcc3_uno-> "uno:unsafe:debug" -debug_uno_uno-> "uno:unsafe" -unsafe_uno_uno-> "uno" -affine_uno_uno-> "uno:affine" -gcc3_uno-> "gcc3:affine". - Always map through the nearest "uno:<purpose>" environment, e.g.
"gcc3:debug:unsafe" <-> "gcc3:debug:affine" => "gcc3:debug:unsafe" -gcc3_uno-> "uno:debug:unsafe" -unsafe_uno_uno-> "uno:debug" -affine_uno_uno-> "uno:debug:affine" -gcc3_uno-> "gcc3:debug:unsafe". - Shortcut if possible, no is mediation necessary, should directly map through purpose, e.g.
"uno:debug:affine" -> "uno:debug" => "uno:debug:affine" -affine_uno_uno-> "uno:debug".
The mapping algorithm does not know any particular purpose. It is just leverages the current purpose API.
Rationale
The introduction of purpose environments allows to instantiate multiple environments of the same ABI (e.g. "gcc3") but with different purposes. Cascaded mappings allows to map between environments of different purposes, by using the Uno runtimes purpose mapping mechanism.
