Next: PLBundle
Up: Player Type
Previous: GlobalDataDef
GlobalDataUse
Semantics
The player type GlobalDataUse corresponds to an imported data object. An imported data object is actually a reference to a global data definition that is located in (i.e., exported by) another component. The data reference has a name and a type. The name refers to the name of the data object as it appears in the definition in the exporting component, and the type describes the expectations that the importing component has regarding the type of the data object (the GlobalDataDef player in the exporting component specifies the actual signature). GlobalDataUse players reference GlobalDataDef players within the boundary of a single process.
Component Types In
GlobalDataUse players can legally be defined in components of the following types:
Role Type
Associations
A player of type GlobalDataUse 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 GlobalDataUse player:
- The syntax for the MaxAssocs property in a GlobalDataUse player is a single <integer> surrounded by parentheses:
- MAXASSOCS (1)
- The syntax for the MinAssocs property in a GlobalDataUse player is a single <integer> surrounded by parentheses:
- MINASSOCS (1)
- The syntax for the Signature property in a GlobalDataUse player is a single <identifier> or "string" surrounded by parentheses:
- SIGNATURE (int)
SIGNATURE ("char *")
Implementation Considerations
An example of a GlobalDataUse player in the implementation would be an external variable reference in a C source code file (in boldface type below):
/* defined, for example, in C include file my_application_globals.h */
extern int a_global_variable;
/* defined, for example, in C source code file my_utility_file.c */
#include "my_application_globals.h"
static int a_local_variable = a_global_variable;
Next: PLBundle
Up: Player Type
Previous: GlobalDataDef
Comments?
Mail the current maintainer of this page.
Author:
Gregory Zelesnik
Last Modified: May 12, 1996