Identifying Problems in Code

The following indicators can help to identify problems in your code. The build process is discussed in detail under Building ProvideX Projects. This section will focus on how error messages are associated with the ProvideX source code.

As a resource is (re)built, information will be updated to the Console view. This view will show a summary of the results of the build process; if there are errors in the source code this summary will include information about the number of errors found. Also, for each error found in the source file, an error line will be added to the Problem view and a marker will be placed in the vertical ruler of your source code.

Build Errors

To demonstrate this process...

1. Open DemoApp > src > prog > outputpdf.pvc.pvt in the editor by double clicking the resource in the Navigator view.

2. Add the following code at the end of the source listing:
   read (x0,err=BadRec)
   x1 = "an error"

3. Click the Save button. The program is rebuilt and the problems found in the source code will be identified in several ways:
   • In the Problems view:
     • An error message "Error #26: Variable type invalid
     • A warning message Warning #123: The following statement labels cannot be located: BadRec
   • In the editor's vertical ruler, problem markers will be displayed near the affected lines; if the mouse hovers over any of these markers, the description text associated with that marker will display
   • The editor scroll-bar is also annotated with problem markers
   • The Console view will display a summary of all warnings/errors from the build process

   

4. Click the close (X) button on the editor's tab to close the editor.

Filtering Errors

When a project contains many application programs, there may be occassions when there are several programs with errors or warnings. Eclipse allows the list of items reported in the Problems view to be filtered to reduce the number of items that are displayed to only those that match the filter criteria.

In the Problems view...

• Press the drop-down button to access the menu and select 'Filters..' to create/maintain filters.

  
  

• Create a new filter, click Rename, end enter a name of 'CurrentAppOnly'.

• Select to limit the scope of the filter to 'On selected element and its children'.

• Make this the active filter and disable any others.

  
  

Correcting Errors

Once the number of items in the Problems view has been reduced to a manageable number...

• Select a problem in the list.
• Open its context menu (right click), and select Go To Resource.
• Or, double-click a problem in the list

The file is opened in the editor at the location of the problem.

Correct the problem in the editor...

• Change the variable "X1" a string variable by adding the "$" character to the X1 variable. The modified line should be similar to:

  x1$ = "an error"

• Click the Save button. The program is rebuilt and the problem indicators disappear.

Notes

You can configure how problems are indicated on the General > Editors > Text Editors > Annotations preference page.

Next Section: Using the Local History