Skip to content

Overview of Compiler Errors

Compiler Errors

This section lists all compiler errors and warnings in numeric order.

Some compiler error or warning numbers can have multiple different but similar causes, and there can be several different error messages listed for any one error number. In that case, the different possible error messages for an error number are listed in alphabetical order.

Example

  • 100 - Maximum Number Of Message/Property Definitions Exceeded
  • 100 - Name_Object Must Precede Class Or Procedure

Error messages without a corresponding number are listed first, in alphabetical order.

The page for each error number and message lists all known possible causes and resolutions for the error, as well as examples where relevant.

If there is more than one possible cause for an error, the causes and resolutions are listed as a numbered list, with a matching cause and resolution having the same number.

Example

Cause

  1. Cause 1
  2. Cause 2

Resolution

  1. This is the resolution for cause 1
  2. This is the resolution for cause 2

When compilation takes place, the compiler may encounter a command line that is logically impossible or that it cannot make sense of in some other way. This is called a compile-time error. Most errors in the use of commands, as well as some typographical errors, are caught at compile time.

Other errors may be caused by the action of the operator, the data which is acted upon by the program, or faulty logic by the programmer. These errors are usually flagged when the compiled program is actually run (runtime). For this reason, compile-time errors and runtime errors are separated into groups. Be sure to consult the appropriate list when trying to diagnose an error.

You can provide your own custom error messages in your compiler by using the #ERROR compiler directive in your command macros. You can also provide non-error output of messages from the compiler with the #REM compiler directive in your programs or commands.