F. CPL Run-Time-Errors
Message numbers starting with 1 are generated by the
script compiler, so in most cases they are syntax errors.
Those numbers starting with 2 are issued by the
pseudo code interpreter.
- 101
Message: No state definitions found in source file
Cause: The script file contains no clause.
A script file must have at least one state definition.
- 102
Message: Initial state must have an definition
Cause: The first state definition in a script
must have an event definition, because it serves
as the entrypoint for the script.
- 103
Message: Multiple enter event definitions for the state 'x'
Cause: More than one clause was found in
a state definition.
- 104
Message: String too long
Cause: The maximum number of characters for a string
has been exceeded, which is defined by the MAX_STRING_LENGTH macro in
iSrvCpl.h. Currently this value is set to 256 characters.
- 105
Message: Unterminated string
Cause: While parsing a string constant an opening quote
was found but no closing one.
- 106
Message: Unexpected end of file
Cause: While parsing a command the end-of-file was detected prematurely.
- 107
Message: Symbol too long
Cause: The maximum number of characters per symbol has
been exceeded, which is defined by the MAX_SYMBOL_LENGTH macro
in iSrvCpl.h. Currently this value is set to 256 characters.
- 108
Message: Zero length variable name
Cause: A sign was found but no variable name.
- 109
Message: Unknown symbol 'X'
Cause: An unknown symbol was found by the parser.
- 110
Message: String expression expected for audio filename
Cause: The filename in an statement is missing.
- 112
Message: '' expected
Cause: The at the beginning of a statement block is missing.
- 113
Message: Operand expected
Cause: An error occured while parsing a condition.
- 114
Message: Operator <, >, ==, >=, <= or != expected
Cause: An error occured while parsing a condition.
- 115
Message: '' expected
Cause: The closing at the end of a statement block
was not found.
- 116
Message: Variable name expected
Cause: The variablename for a , or
statement was not supplied.
- 117
Message: 'x' is a read only variable
Cause: An attempt was made, to assign a value to
a read-only variable using a or command.
- 118
Message: String expression expected
Cause: The 2. parameter of a statement is not a string expression.
- 119
Message: String expression expected
Cause: The 3. parameter of a statement is not a string expression.
- 120
Message: Expected statename
Cause: The state name after an statement is missing
- 121
Message: Eventdefition starting with 'on' expected
Cause: While parsing a statebody an other symbol then
was found.
- 122
Message: String expression expected for match pattern
Cause: After an the match pattern string is missing.
- 123
Message: Timer name expected
Cause: In a clause the timer name is
invalid or missing.
- 124
Message: Expected event specification
Cause: After an a symbol other than ,
, , or was found.
- 125
Message: Command string expression expected
Cause: The string expression in a statement
is invalid or missing.
- 126
Message: String expression expected
Cause: The 1. parameter of an statement is not a string expression.
- 127
Message: String expression expected
Cause: The 2. parameter of an statement is not a string expression.
- 128
Message: String expression expected
Cause: The 3. parameter of an statement is not a string expression.
- 129
Message: String expression expected
Cause: The string argument for a statement
is invalid or missing.
- 130
Message: Procedure name expected
Cause: An invalid or no procedure name was found in a
definition.
- 131
Message: Statement block beginning with '' expected
Cause: The at the beginning of a statement block is missing.
- 132
Message: String expression expected for destination
Cause: The string expression in an statement is
invalid or missing.
- 133
Message: String expression expected
Cause: The string expression in an statement is
invalid or missing.
- 134
Message: Statename expected
Cause: An invalid or no state name was found
in a definition.
- 135
Message: '' expected
Cause: An other symbol than was found after the
state name in a state definition.
- 136
Message: The are no event definitions for state 'x'
Cause: An empty state definition was found. A state
definition must have at least one event definition.
- 137
Message: Statement expected
Cause: An invalid statement has been found in a statement block.
- 138
Message: Timer name expected
Cause: An invalid timer name was found in a
statement.
- 138
Message: String expression expected for timeout
Cause: In a timer statement the timeout string
expression after the / was missing.
- 139
Message: Expected 'local', 'global' or 'stop'
Cause: In a statement a symbol other than
, or was
found after the timer name.
- 140
Message: Undefined state name
Cause: The state name used in an statement
is not declared within the script file, i.e. there is no state
definition using this name.
- 141
Message: Undefined proc name
Cause: The procedure name used in an statement
is not declared within the script file, i.e. there is no procedure
definition using this name.
- 142
Message: Unexpected symbol
Cause: An other symbol than , or
was found outside a or block.
- 201
Message: Variable 'x' not declared
Cause: A variable has been referenced which has
not been assigned a value previously. Use the statement
to assign a value to a variable.
- 202
Message: Illegal CPL instruction, PC=xxxx
Cause: An illegal op code was found by the
pseudo code interpreter. The script execution stopped at
program counter xxxx. Use the cpldebug program to
determine the exact location.
- 203
Message: Can't open file 'x' for recording audio
Cause: The file named 'x' could not be opend for
recording the incoming audio stream. Check permissions!
- 204
Message: Error forking in server process
Cause: The fork() system call for an
command failed.
- 205
Message: Too many timers active at the same time
Cause: The maximum number of concurrently active timers
has been exceeded. This value is defined by the
MAX_TIMERS macro in the iSrvCpl.h file and is currently
set to 10 concurrent timers.
- 206
Message: Unexpected URL type in destination specification
Cause: An invalid URL type was found in the destination
address of a statement.
- 207
Message: Syntax error in URL 'x'
Cause: The URL you passed to a statement
has an invalid syntax.
File was created Wed Feb 26 18:31:48 1997 by tex2html