The EGL V6.0 migration tool converts EGL source from V5.1.2 and V6.0 to
comply with the EGL V6.0 iFix. Additional changes for EGL V6.0.1 are described
at the end of this topic.
Note: Do not use the migration tool on code that
has already been updated to the EGL V6.0 iFix. Doing so can create errors
in your code.
The migration tool can be used on an entire project, a single file, or
a selection of files. Running the tool on a package or folder converts all
of the EGL source files in that package or folder. For more information on
the code that is changed by the migration tool, see EGL-to-EGL migration.
To migrate EGL code to the EGL V6.0 iFix, do as follows:
- In the workbench, click Window > Preferences.
- On the left side of the Preferences window, expand Workbench and
click Capabilities.
- From the list of capabilities, expand EGL Developer.
- Select the check box for the capability named EGL V6.0 Migration.
- Click OK.
- Again, click Window > Preferences.
- On the left side of the Preferences window, expand EGL and click EGL
V6.0 Migration Preferences.
- Set the preferences for the EGL V6.0 migration tool. For more information
on the preferences in this window, see Setting EGL-to-EGL migration preferences.
- In the Project Explorer view or the Navigator view, select the EGL projects,
packages, folders, or files you want to migrate. You can select any number
of EGL resources to migrate. To select more than one resource at once, hold
CTRL while clicking the resources.
- Right-click on a selected resource and click EGL V6.0 Migration > Migrate from
the popup menu.
- Inspect your code for places that do not comply with the EGL V6.0 iFix.
The migration tool converts the selected EGL source files to comply with
the EGL V6.0 iFix. To review the changes that the tool made to the source
code, do as follows:
- In the Project Explorer view or the Navigator view, right-click an EGL
source file that has been migrated and click Compare With > Local History from
the popup menu.
- Examine the differences between the file in the workspace and the previous
version.
- When you are finished reviewing the changes, click OK.
After you use the EGL V6.0 migration tool, make sure that none of your
identifiers (such as variable or part names) begins with the at sign (@),
which is now used as the first character of a complex property. Also, if you
migrated code from VisualAge® Generator, you may need to change StrLib.compareStr to VGLib.compareBytes, StrLib.copyStr to VGLib.copyBytes, and StrLib.concatenate to VGLib.concatenateBytes;
but a change is needed only when the last argument in the existing invocation
is a numeric value, as evidenced by an error message that indicates a problem
with the argument's primitive type.