MFPLI00140 - MFPLI00159
MFPLI00140U The size of a dope-vector exceeds the implementation's limit. Either eliminate the use of * extents in this ENTRY point, or pass STRUCTUREs by passing a POINTER to them.
The size of a dope-vector exceeds the implementation's limit.
MFPLI00141W "parameter-name" is an undeclared parameter. It has been declared in its containing block and will acquire default attributes.
Parameters listed in an internal procedure parameter list must be declared within that procedure.
MFPLI00142W "entry-name" has been declared with a RETURNS attribute but no ENTRY attribute. An ENTRY attribute has been supplied.
The ENTRY attribute, without a parameter descriptor list, is implied by the RETURNS attribute.
MFPLI00143W "variable-name" has been declared without a data type. The default type has been supplied.
The default data type has been supplied for "
variable-name
", declared without a data type.
MFPLI00144E "variable-name" has been declared with a nonzero scale-factor. A zero scale-factor has been supplied.
Fixed-point binary numbers with fractional parts are not supported.
MFPLI00145W The INITIAL attribute specified for "variable-name" cannot be applied to variables of this storage class; INITIAL attribute ignored.
Defined and parameter variables do not have their own storage and so cannot be initialized.
MFPLI00146S All functions must have a return descriptor with constant size.
Functions may not return strings with adjustable lengths or AREAs with adjustable sizes.
MFPLI00147S "array-name" is an ENTRY or FILE constant and as such it cannot be declared with a DIMENSION attribute.
Although arrays of ENTRY and FILE VARIABLEs are permitted, ENTRY and FILE constants must be scalars.
MFPLI00148S An expected optionally signed short integer was not found.
MFPLI00149S "array-name" has been declared with mixed asterisk and constant bounds. If any bound is an asterisk, all bounds must be asterisks.
MFPLI00150S "variable-name" has been declared FLOAT with a scale-factor. The scale-factor will be ignored.
Scaling factors are only used for fixed-point variables.
MFPLI00151S "variable-name" has been declared with a negative size. A size of one has been supplied.
Strings must not have negative lengths and AREAs must not have negative sizes.
MFPLI00152S "variable-name" is undeclared and has been used in an ALLOCATE or LOCATE statement as the name of a BASED or CONTROLLED variable.
Variables cannot be implicitly declared as BASED or CONTROLLED.
MFPLI00153S "variable-name" cannot be allocated because no SET option or implied SET option is available.
The SET option was not specified in the declaration of "
variable-name
" nor on the ALLOCATE or LOCATE statement.
MFPLI00154S "variable-name" cannot be allocated because no IN option or implied IN option is available.
MFPLI00155S "variable-name" cannot be allocated because the SET option or implied SET option does not reference a POINTER or OFFSET variable.
Either a POINTER or OFFSET variable must be specified in the SET option in the declaration of a BASED variable or in the SET option on the ALLOCATE or LOCATE statement.
MFPLI00156E An ALLOCATE statement for the CONTROLLED variable "variable-name" cannot specify the SET option. The SET option has been ignored.
The SET option may only be specified on ALLOCATE statements for BASED variables.
MFPLI00157S "variable-name" cannot be allocated because it is neither a BASED nor a CONTROLLED variable. Only BASED or CONTROLLED non-member variables can be allocated by an ALLOCATE statement.
Only BASED and CONTROLLED variables can be allocated and "
variable-name
" is neither BASED nor CONTROLLED.
MFPLI00158S All RETURN statements in a function must return values.
MFPLI00159S A RETURN statement in a subroutine cannot return a value.
Parent topic:
MFPLI - PL/I Compiler Messages