VisualAge Generator to Enterprise Generation Language Migration Guide

When and how part names are resolved

At definition time, VisualAge Generator does not require that all parts exist. In the program structure diagram, VisualAge Generator indicates missing maps, records, tables and functions with a question mark. However, in other places such as the use of a shared data item, there is no indication if the part does not currently exist. When you save a part in VisualAge Generator, there is some basic syntax validation, but there is no cross-part validation until you test, validate, or generate. In EGL, whenever you save a file, there is more extensive validation -- including validation that all part names can be resolved. This gives you the earliest possible warning when there is a problem.

VisualAge Generator searches all parts in the workspace to find a particular part name. If there are duplicate part names in VisualAge for Java, then test and generation stop until the duplicate part problem is fixed. VisualAge for Smalltalk does not permit you to load duplicate parts into the image. In EGL, you are permitted to have duplicate part names in your workspace. EGL uses a combination of the EGL build path for a project, import statements in a file, and the containerContextDependent property for records and functions to determine which definition of a part to use.

The migration tool sets the EGL build path for projects and includes import statements in files based on the available parts in the migration set. To obtain the correct EGL build path and import statements, always include all the associated parts when you migrate. For example, when you migrate a program, be sure to include all the parts that you need to generate the program in VisualAge Generator. This ensures the best possible migration of your parts. See the following sections for more details:


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]