Use Compile Warning List (-cwl) to alert users to the occurrence of specified statements in the source code. For example, you might want to flag the occurrence of deprecated statements, to discourage their use in favor of new alternative statements.

filename

The name of a file that contains ABL statements that are to trigger a warning if they are found in the source code at compile time. Each statement must use a single line in the file. OpenEdge uses the PROPATH variable to locate filename. If it cannot find filename, it displays an error message and does not start.

When source code containing one or more instances of the specified statements is compiled, OpenEdge displays a message box containing a warning for each such instance, in the following format:

The flagged_statement statement from the compile warning list was found in file
  file_name at line line_number. 

Where:

• flagged_statement is the statement matching an entry in the Compile Warning List file
• file_name is the source file containing the flagged statement
• line_number is the line in the source file where the flagged statement occurs

The user can click OK in the message box to continue. Compilation occurs normally

You can specify that a warning should occur only if the statement includes specific phrases or options. To do so, add those phrases or options to the entry in the list. For example, the following entry results in a warning only for instances of the DEFINE FRAME statement that include the SHARED option:

DEFINE SHARED FRAME

In the preceding example, simple DEFINE FRAME statements do not raise a warning message. However, the statement DEFINE NEW SHARED FRAME does result in a warning; even though the syntax does not exactly match the list entry, OpenEdge recognizes it as an instance of the flagged DEFINE SHARED FRAME statement.

Statements found in comments do not trigger warning messages.