The gmPL utility statements are like the command statements in that they are used
within a gmBasic command script. Their role, however, is not to guide a translation
but rather to perform a special operation to eventually aid a translation. The utility statements
are as follows:
Statement
Description of use
BuildOrder
Reviews and orders a set of loaded project files so that they
can be processed.
GlobalStubs
Authors the stubs for a set of references that have been loaded previously via
the Reference command.
Gmsl
Introduces Great Migrations Scripting Language gmSL subprograms that can
then be executed.
ImportList
Rather than authoring any local stubs with the translated codes gmBasic can
instead manage an ImportsGlobal file which maintains a list of all referenced components
in all imported references. Once completed, this statement authors the stub code for them
IncludeOrder
Reviews and orders a set of loaded ASP files so that they can
be processed.
Load
Loads the source compilation units so that they can be edited
or ordered in preparation for processing.
Search
Searches a virtual binary information file for symbols and produces reports as requested
within the statement.
SharedFile
Used after a set of VBP files have been loaded with the SourceCode attribute turned on.
It scans the loaded form, class, and module files to see if any are loaded by more
that one project.
gmNI-Utility
Whenever gmBasic encounters a statement in a command script that it does not recognize,
it searches each loaded runtime DLL for a handler of that statement. This makes it possible
to add utility statements as needed by code migration projects.