Agents in SCOOP - Revision history

Peter gummer: Fix typo

2013-05-07T22:08:35Z

Fix typo

2013-05-07T07:58:54Z

‎Types

2013-05-07T07:58:03Z

‎Types

2013-05-07T07:57:19Z

‎Status of agent targets

2013-05-07T07:56:32Z

‎Status of a target

2013-05-07T07:56:14Z

‎Status of a target

2013-05-07T07:55:40Z

‎Types

2013-05-07T07:52:51Z

Improved phrasing

2013-03-25T16:56:47Z

‎Agent classes: Changed separateness status of TUPLE to be non-separate.

2013-03-25T16:56:14Z

‎Types: Changed separateness status of TUPLE to be non-separate.

@@ Line 2: / Line 2: @@
 == Status of agent targets ==
-: Because any agent object is created on a processor associated with the agent's target, that target hasto be controlled.
+: Because any agent object is created on a processor associated with the agent's target, that target has to be controlled.
 '''Agent target validity rule.''' The target of an agent must be controlled.

@@ Line 21: / Line 21: @@
 </e>
-: The first parameter is not separate because both a target and an agent object run on the same processor.
+: The first parameter is not separate because the target and the agent object have the same handler.
 : The separateness status of the type <e>TUPLE</e> used for arguments does not matter, what matters is the types of arguments. In many cases when <e>TUPLE</e> is used, it is used as a value type, i.e. it could even be an expanded type, so that a separate mark is not required. But then we need some conversion rules to attach different types of <e>TUPLE</e>. In order to avoid unnecessary processor dependency, it's going to be created on the target processor (as a routine object itself), therefore it is not <e>separate</e>.

@@ Line 7: / Line 7: @@
 == Types ==
 '''Agent argument types validity rule.''' If an agent has a separate target, every non-expanded argument of the associated feature must be separate.
-: Because an agent is created on a processor of a target, without processor tags it's impossible to create an agent on an open target of separate type and then pass the corresponding target object at the agent call. Also there is no way to make an open target controlled.
+: Because an agent is created on a processor of a target, without processor tags it is impossible to create an agent on an open target of separate type and then pass the corresponding target object at the agent call. Also there is no way to make an open target controlled (see previous rule).
 '''Agent open target type validity rule.''' If the target of an agent is open, it may not be separate.

@@ Line 2: / Line 2: @@
 == Status of agent targets ==
-: Because a agent object is created on a processor associated with a target, this processor needs to be controlled.
+: Because any agent object is created on a processor associated with the agent's target, that target hasto be controlled.
 '''Agent target validity rule.''' The target of an agent must be controlled.

@@ Line 1: / Line 1: @@
 The page reflects current decisions taken for the current SCOOP implementation, in particular without support for processor tags. So it may change in the future.
-== Status of a target ==
+== Status of agent targets ==
 : Because a agent object is created on a processor associated with a target, this processor needs to be controlled.
 '''Agent target validity rule.''' The target of an agent must be controlled.

@@ Line 8: / Line 8: @@
 '''Agent argument types validity rule.''' Formal arguments of a feature used in an agent expression with a separate target are separate.
 : Because an agent is created on a processor of a target, without processor tags it's impossible to create an agent on an open target of separate type and then pass the corresponding target object at the agent call. Also there is no way to make an open target controlled.
-'''Agent open target type validity rule.''' An open target of an agent is not separate.
+'''Agent open target type validity rule.''' If the target of an agent is open, it may not be separate.
 '''Example.''' <e>

@@ Line 28: / Line 28: @@
 '''Example.''' The agent type from the example above becomes<e>
-       separate FUNCTION [separate TUPLE [separate Q], separate R]
+       separate FUNCTION [TUPLE [separate Q], separate R]
 </e>

@@ Line 18: / Line 18: @@
 </e>
 The type <e>t</e> of <e>agent t.f (c, ?)</e> is <e>
-       separate FUNCTION [ANY, separate TUPLE [separate Q], separate R]
+       separate FUNCTION [ANY, TUPLE [separate Q], separate R]
 </e>
 : The first parameter is not separate because both a target and an agent object run on the same processor.
-: The separateness status of the type <e>TUPLE</e> used for arguments does not matter, what matters is the types of arguments. In many cases when <e>TUPLE</e> is used, it is used as a value type, i.e. it could even be an expanded type, so that a separate mark is not required. But then we need some conversion rules to attach different types of <e>TUPLE</e>. So far the implementation uses whatever separateness status of a <e>TUPLE</e> type is more suitable, most probably it is <e>separate TUPLE</e>.
+: The separateness status of the type <e>TUPLE</e> used for arguments does not matter, what matters is the types of arguments. In many cases when <e>TUPLE</e> is used, it is used as a value type, i.e. it could even be an expanded type, so that a separate mark is not required. But then we need some conversion rules to attach different types of <e>TUPLE</e>. In order to avoid unnecessary processor dependency, it's going to be created on the target processor (as a routine object itself), therefore it is not <e>separate</e>.
 == Agent classes ==