HP Pascal/iX Reference Manual (31502-90022)

A-: 1
Appendix A Error Messages
On HP-UX, error messages and their explanatory text are in the file named
/usr/lib/paserrs . To list this file, use the command:
cat usr/lib/paserrs
On MPE/iX, error messages and their explanatory text are in the file
named PASXLCAT.PUB.SYS . To list this file, use the command:
:PRINT PASXLCAT.PUB.SYS
In reading the error messages, note that:
* A dollar sign ($) in the left margin indicates a comment line
containing explanatory text.
* An exclamation mark (!) indicates that an item is variable. The
compiler substitutes a specific item for the exclamation mark when
it issues the message.
Example
043 THIS FEATURE REQUIRES $OS ! (043)
$ 1. This feature is not available under the current OS level
060 OPERAND NOT OF TYPE BOOLEAN (060)
$ 1. A non-Boolean operand appears with the operator NOT, OR,
$ or AND.
When the compiler issues error message 43, it will substitute an OS level
for the exclamation mark; for example:
THIS FEATURE REQUIRES $OS 'HPUX'$
Finding Undetected Errors
The following errors are currently undetected by the compiler at compile
time or by the system at run time. In any future release, an undetected
error may become a detected error.
Errors that are only detected when the ANSI option is ON, or when
STANDARD_LEVEL is set to ANSI, do not appear on this list.
There is no significance to the order in which errors are listed here.
1. Each component of a structured function result must be assigned a
value in the body of the function.
2. If assignment to a function result is conditional, it must occur
at run time.
3. A control variable in a FOR statement cannot be changed in the
statement after DO by calling a procedure or function with a
nonlocal reference to the variable.
4. A parameter of dispose cannot be an actual variable parameter, an
element of a record variable list of a WITH statement, or both.
Similarly, a dynamic variable in a region of the heap deallocated
by release cannot fall in one of these categories.
5. When the tag field of a record with variants is changed, all
previous variants become undefined.
6. For records with tagless variants, reference to a field for a
particular variant means that other previous variants become
undefined.
7. All possible record variants must be specified in a record
declaration.