The program has specified conflicting size attributes for this object. For example, the following declaration is erroneous because of the attempt to extend the attribute size of the type 'smaller':

Correct the attribute size.

Both bounds of a subrange declaration must be of the same ordinal type (single character or integer). If the subrange bounds types are different or if they are not ordinal types, the preprocessor will use the type of the second bound and accept the usage of variables declared with this subrange type. This will cause an error in later Pascal compilation.

Ensure both bounds of the subrange declaration are of the same ordinal type.

You may have an end statement that is not balanced by a subprogram header (for example, PROGRAM, PROCEDURE, FUNCTION, or MODULE). These subprogram delimiters provide scoping for Pascal variables and labels generated by the preprocessor. If you had any syntax errors on the subprogram header statement, then correct those errors and preprocess the file again.

Ensure that the subprogram headers and end pairs are balanced.

You must issue the ## declare statement before the first embedded statement. The preprocessor generates code that references procedures and functions declared in a file included by the
## declare statement. Without issuing the
## declare statement, the Pascal compiler will not accept those references.

Ensure that the ## declare statement is included and issued before the first embedded statement.

A string referenced in an embedded statement must be either a packed array of char, a varying of char, or a single char. You have used a non-packed array of char as an embedded string variable.

Convert the variable declaration to either packed or varying, or subscript the array to reference only one element.

Only one semicolon is allowed between components of a record declaration. The preprocessor ignores the extra semicolons.

Delete the extra semicolon in your source code.

You have not referenced the specified variable with the same number of subscripts as the number of dimensions with which the variable was declared. This error indicates that you have failed to subscript an array, or you have subscripted a non-array. The preprocessor does not parse declaration dimensions or subscript expressions.

Correct the code.

This error occurs when the address or value of a variable is incorrectly expressed because of faulty indirection. For example, the name of an integer pointer has been given instead of the variable that the pointer was pointing at.

Either redeclare the variable with the intended indirection (and check any implicit indirection in the type), or change its use in the current statement.

The Pascal preprocessor must take a second pass in order to declare implicitly generated labels. If the source file referenced embedded INCLUDE files, then the second pass needs to generate labels into those files. Consequently there is a maximum nesting limit of INCLUDE files.

Try reorganizing your files to create a flatter source file structure.

The Pascal preprocessor must take a second pass in order to declare implicitly generated labels. If labels were implicitly generated then the preprocessor needs to know where to declare them on the second pass. That is why one must precede subprogram headers (PROGRAM, PROCEDURE, FUNCTION and MODULE) with ##, or use the LABEL statement. If you did not declare your subprogram header to the preprocessor, the generated labels will be marked as undeclared by the Pascal compiler.

Correct the code.

The Pascal preprocessor must take a second pass in order to declare implicitly generated labels. Because there is a temporary file involved, and this file has a fixed name, you should avoid running the preprocessor more than once in the same directory. This error may also occur if the intermediate file disappeared, the system protections of the current directory are too restrictive or have changed, or if the original input file was moved between the first and second pass of the preprocessor.

Correct the code.

The Pascal preprocessor must take a second pass in order to declare implicitly generated labels. There was a difference between the number of label declaration sections the preprocessor expected to generate and the number of markers found in the intermediate file. This may be caused by an embedded include statement that requires its own scope for label generation.

If there were nested include statements whose files required labels, try to flatten them out into larger source files.

You did not use the specified keyword, or you did not make the word known to the preprocessor. If there are no other errors the preprocessor will generate correct Pascal code.

Ensure the indicated keyword is specified and made known to the preprocessor.

You cannot nest modules and programs in themselves or each other.

Ensure you have placed the ## mark before the end statement for programs and modules.

If this really is a variable you should make its declaration known to the preprocessor.

You have used array subscription on a name that was not declared as a Pascal variable to the preprocessor.

If this really is a variable you should make its declaration known to the preprocessor.

Elements of a varying-length character string array cannot be passed to the runtime system.

If you need to pass a single element then declare the array as a plain array (not PACKED or VARYING).

Pascal requires that bounds expressions of conformant arrays be of a scalar type.

Choose a scalar type, such as a single character or an integer.

You have used the specified name as an embedded variable, but you have not declared it to the preprocessor. This may also be a scope problem.

Make sure you have typed the name correctly, declared the variable to the preprocessor and have used it in its scope.

The declaration of a comma-separated list of names in a declaration is too long. For example:

Try breaking up the declaration into groups.

If you need to use PARAM target lists, then you should write this subprogram in another host language (such as C or Fortran) and link that module with your Pascal program.

The ## declare statement should occur only once per module. Placing the statement after an EQUEL statement will also cause this error.

Ensure that the ## declare statement is issued only once.

Earlier versions of EQUEL/Pascal did not require the use of a semicolon after the label statement. The preprocessor now requires the terminating semicolon if you include a list of your own labels with the label statement. If you do not include the semicolon, the preprocessor will generate correct code, but you should still correct the error.

Ensure that a semicolon ends the label declaration list.

The last record member referenced is not a member of the current record.

Make sure you have spelled the member name correctly, and that it is a member of the specified record.

The end of the file was reached with some program blocks left open.

Make sure you have an end statement for each subprogram header or embedded LABEL statement.

The specified TYPE or CONST name has not yet been declared.

Make sure that all types and constants are defined before use. Forward type declarations (such as pointers to undefined types) are an exception.

The stack used to store comma-separated names in declarations has been corrupted.

Try rearranging the list of names in the declaration.

You may declare variables of type set and quadruple, but you may not use them in embedded statements. The declarations are only allowed so that you can declare records with components of those types.

If those variables need to interact with Ingres, then declare the set variable as an array of boolean, and the quadruple variable as a double.

The specified name is not known to the preprocessor when used with an embedded with statement.

Check the spelling of the with statement and make sure it was declared to the preprocessor in the correct scope.

You have nested embedded with blocks too deeply.

Flatten your record declarations, or use partially qualified names in place of the deepest with statement.

Every with block must be closed by an end statement. This error indicates that the end of a routine has been encountered before a with block inside the routine has been ended.

Ensure that every with block is closed by an end statement.

A with statement specified a variable that was not a record.

Check the name and verify that the scoping rules ensure that this use of the specified name refers to a record variable.

The stack used to manage a with record has been corrupted.

Try rearranging the nesting of with statements, or partially qualify some of the more deeply nested record components.

The named variable refers to a record. It was used where a variable must be used to retrieve data from Ingres. This error may also cause a syntax error on any subsequent record components that are referenced.

Correct the use of the variable.