The RenderMan Interface - Paul Bourke

adhandle
badparamlist
badripcode
badstringtoken
badtoken
badversion
limitcheck
An invalid light or object handle was supplied as a parameter to an
Illuminate, ObjectInstance, LightSource, AreaLightSource, or ObjectBegin
request. For Illuminate, the light handle must be an integer
value specified in a previous LightSource or AreaLightSource
request. For ObjectInstance, the object handle must be an integer
value specified in a previous ObjectBegin request. For LightSource,
AreaLightSource, and ObjectBegin this error is raised if the number
specified for a light handle is significantly larger than any previous
handle; for example, specifying 3000 when the largest previous handle
was 10 (this is used as a “sanity check” to guard against corrupted
input data).
EXAMPLE
LightSource ”finite” 1
Illuminate 99999
In a token-value pair of a parameter list, the type of a value did not
agree with the declared type of the token.
EXAMPLE
Declare ”gridsize” ”uniform float[2]”
Option ”limits” ”gridsize” ”not a number”
A binary encoded token that specified a RIB request used an undefined
request code. Request codes must be defined, prior to their use,
with the binary encoding protocol; see the section on Binary Encoding.
A binary encoded string token referenced a string that had not previously
been defined. The binary encoding scheme is described in
Binary encoding.
A byte with the most significant bit set was not recognized as a valid
binary encoding. The binary encoding scheme is described in Binary
encoding.
EXAMPLE
\300
The RIB protocol version number specified in a version request was
greater than the protocol version number of the interpreter. SEE ALSO
version
An internal limit was encountered during normal operation of the interpreter.
Implementers of RIB interpreters are expected to avoid imposing
arbitrary limits. Some implementations may, however, need to
limit the maximum size of strings, arrays, etc. due to memory constraints.
182