ABAP Keyword Documentation → ABAP - Release-Specific Changes → Changes in Releases 6.xx → Changes in Release 6.40
ABAP Objects in Release 6.40
1. Data types and constants in the public visibility section
2. Access to static components for object types of global classes
3. Use of alias names
4. Unused private components
Other versions: 7.31 | 7.40 | 7.54
Modification 1
Data Types and Constants in the Visibility Section of Global Classes
From Release 6.40, data types and constants can be created in the public visibility section of global classes and interfaces, which was not previously possible. Classes and interfaces therefore make the use of type groups superfluous, whereas for types and constants names that are longer than the names in the type groups are possible.
Modification 2
Access to Static Components of Object Types
The statements CLASS cl DEFINITION LOAD and INTERFACE in LOAD are now only necessary if source code contains recursive accesses to global classes or interfaces. Until now, these statements always had to be specified if static components of global classes or interfaces were being accessed for the first time. Transaction SYNT, to which a trace for these object types has been added, can be used to detect recursive class and interface definitions.
Note
This change was also transported back to Release 6.20.
Modification 3
Use of Alias Names
From Release 6.40, it is possible to specify the alias names of the methods defined using
ALIASES in the implementation of methods using the statement METHOD and in the
redefinition of methods
using the statement METHODS ...REDEFINITION. At the same time, however, from
Release 6.40 there will be a warning about the syntax check if identical components are accessed within a class declaration or a method with different names.
Modification 4
Unused Private Components
From Release 6.40, all unused private components of a class produce a warning in the extended program check. Private methods must be called and private events must be both raised and handled.