Difference between revisions of "Uno/Spec/Environment Stack"
m (→Feature: Minor correction.) |
m (→Feature: Moved text from Uno/Spec/Threading Model here.) |
||
| Line 5: | Line 5: | ||
=== Feature === | === Feature === | ||
| − | The [[../Runtime|Runtime]] allows to enter / leave a particular [[../Purpose Environment|Purpose Environment]], respectively to invoke functions in the [[../Purpose Environment|Purpose Environment]]. | + | The [[../Runtime|Runtime]] allows to enter / leave a particular [[../Purpose Environment|Purpose Environment]], respectively to invoke functions in the [[../Purpose Environment|Purpose Environment]]. The current (purpose) environment does not only vary with the languages ABI (e.g. Java or C++), but also with the executed codes declared purpose type. |
=== Rationale === | === Rationale === | ||
Revision as of 13:05, 16 June 2006
state: draft
type: specification
Environment Stack
Feature
The Runtime allows to enter / leave a particular Purpose Environment, respectively to invoke functions in the Purpose Environment. The current (purpose) environment does not only vary with the languages ABI (e.g. Java or C++), but also with the executed codes declared purpose type.
Rationale
Operations may need to be associated with the Uno/Spec/Environment(s) of a particular object. Such operations may set thread related global variables (e.g. the component- or current-context) or may acquire mutexes.
API
-
getCurrentEnvironment- Provides the current active Uno/Spec/Environment, in case no Uno/Spec/Environment has been entered, the Thread safe environment is returned. -
invoke- Invokes the passed function in the given Uno/Spec/Environment. -
enter- Enters the given Uno/Spec/Environment. Uno/Spec/Environment can be left by entering another [../
Eenvironment]].
-
isValid- Checks if the passed Uno/Spec/Environment is active, so that objects belonging to this Uno/Spec/Environment may be called.
Comment
The enter / leave functionality may not be appropriate for all environments at all times. E.g. the thread affine environment does not allow to be entered, while it already has a thread associated.
