Lazy Loading of Programs for Release 7.0, EhP2
When compiling an ABAP program before Release 7.0, EhP2 , all
associated include programs were loaded when first accessing a global
class, a global interface, or a type group. These includes contain
declarations of the corresponding class, interface, or type pool
which can be used globally.
As of Release 7.0, EhP2 , these include programs are not loaded
until an element declared in them is actually required. For example, a
class class is no longer loaded when a TYPE REF TO class
type reference is made, but when a component of the class is accessed or
the class itself.
This internal optimization of the ABAP Compiler has the
following additional consequences:
1 The TYPE-POOLS statement is obsolete
2 The LOAD addition for CLASS and INTERFACE is
obsolete
ABAP_MODIFICATION_1 The TYPE POOLS statement is obsolete
The TYPE POOLS statement is no longer
required for the use of a data type, a constant, or a macro from a type
group. The elements of a type group can now be addressed in the same way
as all other objects in ABAP Dictionary without previously loading the
type group.
TYPE POOLS statements are ignored by the ABAP Compiler
as of Release 7.0, EhP2 , and can be deleted.
In list processing in particular, the include programs <(><<)>LIST>,
<(><<)>SYMBOL>, <(><<)>ICON>, <(><<)>LINE>, and <(><<)>COLOR> are no
longer needed, since they only contain TYPE-POOLS statements.
ABAP_MODIFICATION_2 The LOAD addition for CLASS
and INTERFACE is obsolete .
The now rarely used statements
CLASS ... DEFINITION LOAD.
INTERFACE ... LOAD.
are no longer required
As of Release 7.0, EhP2 these statements are ignored by the
ABAP Compiler and can be deleted.
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved