Next: RoutineCall
Up: Player Type
Previous: ReadFile
ReadNext
Semantics
The ReadNext player type corresponds to data being read sequentially from the front of a sequential file. Since a sequential file is a passive object that simply contains data, there is no corresponding implementation of this player type in the underlying implementation of a system. It represents an abstraction in UniCon used to describe the action of data being read from a file.
Data can be read sequentially from a file in UniCon by a Filter component via a Pipe connection, and by a Module component via a FileIO connection. The ReadNext player type describes data being read from a file in either situation.
Component Types In
A player of type ReadNext can legally be defined in components of the following types:
Role Type
Associations
A player of type ReadNext can legally be associated with the following role types in connections of the specified type:
Properties
The following properties can be legally included in the property list of a ReadNext player:
- The syntax for the MaxAssocs property in a ReadNext player is a single <integer> surrounded by parentheses:
- MAXASSOCS (1)
- The syntax for the MinAssocs property in a ReadNext player is a single <integer> surrounded by parentheses:
- MINASSOCS (1)
Implementation Considerations
There are no implementation considerations for this player type because there is no correspondence between a ReadNext player type and anything in the underlying implementation of a system.
Next: RoutineCall
Up: Player Type
Previous: ReadFile
Comments?
Mail the current maintainer of this page.
Author:
Gregory Zelesnik
Last Modified: May 12, 1996