Common Runtime Errors; Array Out Of Bounds - Crestron SIMPL+ Reference Manual

Language reference guide
Hide thumbs Also See for SIMPL+:
Table of Contents

Advertisement

Crestron SIMPL+

Common Runtime Errors

Language Reference Guide - DOC. 5797G
®
Common Runtime Errors Overview
The following errors will occur at runtime. In order for these error messages to be
seen, the Crestron Viewport must be open and communications with the control
system (via Ethernet or the computer port) must be established.

Array out of bounds

An attempt was made to access an element of an array that is outside the declared
range of the array. For an array size declaration, the allowable indices are 0 through
the declared size. For example, INTEGER X[10][10] would allow access to X[0][0]
through X[10][10].
Bad printf format
The MAKESTRING or PRINT functions have encountered an invalid character
following the % character. The most common reason for this is when a % is actually
required, %% should be used to print a single % character. Refer to MAKESTRING
and PRINT for a full list of valid format specifiers.
Full Stack
The SWITCH construct may only have 32 CASE statements in SIMPL+ Version
1.00. If more than 32 are used, this error appears.
Library not found
This occurs when a module tries to call a user-defined function that exists in an
external library which was specified with #CRESTRON_LIBRARY or
#USER_LIBRARY. During compilation, the compiler builds a file containing the
libraries to send to the control system. Typically, this could be caused by a transfer
error which would be seen at load time.
Rstack overflow
The Rstack that this message refers to is the Return Stack. When an event is
interrupted by some means (via a process_logic statement or an implied task switch
from inside a loop), information about that event is put on the Return stack, so that
when the event resumes, it knows how to continue. When the event continues, the
saved information is removed from the return stack.
If during this interruption the event is called again, and interrupted again, more
information is saved on the return stack. The return stack is of limited size and if this
keeps occurring, the Return stack will not have enough space to contain more data
and this message will be issued.
For a further discussion of how to handle the programming when events are
interrupted, refer to "Task Switching" on
page
22.
Software
®
SIMPL+
277

Advertisement

Table of Contents
loading

Table of Contents