VisualAge for Java compiles source code incrementally. If you save source code that has a compiler error (also called an unresolved problem), VisualAge for Java displays a warning message. As a result, you see errors immediately.
You can cancel the save operation. In some cases, you can also save the source with the error. However, you cannot save the source in the following cases:
When you fix an unresolved problem, VisualAge for Java fixes the problem throughout the workspace. This means that many unresolved problems disappear for you as you write code.
Even though a class contains unresolved problems, you may be able to run it. The debugger may open and suspend the program during execution.
Unresolved problems occur for many reasons, for example:
If you save a class that contains an unresolved problem, the class is marked with .
If you save a method that has an unresolved problem, the method is marked with . If the class of the incorrect
method has no unresolved problem of its own, it is marked with
.
VisualAge for Java maintains a list of all the classes and methods that have unresolved problems and updates it when you save new or modified code. You can view the list from the Unresolved Problems page of the Workbench and fix the problems there. As well, anywhere where you can select the class or method and see its source (except in a view of the repository) you can modify the source to fix the problem.
Development Without Files
Incremental Compilation
Creating a Class
Creating a Method
Creating an Applet or Application
Finding and Fixing Problems
Importing Files from the File System
Saving Changes to Code
Debugging During the Development Cycle with the Integrated
Debugger