Get Example source ABAP code based on a different SAP table
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
ABAP_MODIFICATION_1 - Data types and constants in visibility section of global classes
As of 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.
ABAP_MODIFICATION_2 - Access to static components of object types
The statements CLASS cl DEFINITION LOAD and INTERFACE in LOAD are now only necessary if a source text contains recursive accesses to global classes or interfaces. Until now, you always had to specify these statements if you were accessing the static components of global classes or interfaces for the first time. To recognize recursive class and interface definitions, you can use transaction SYNT, which has been enhanced with a trace for these object types.
Latest notes:- This change was also retransported after Release 6.20.
ABAP_MODIFICATION_3 - Use of alias names
As of Release 6.40, during the implementation of methods using statement METHOD and during the redefinition of methods with statement METHODS ...REDEFINITION and ALIASES, you can specify the defined alias names of the methods. At the same time, however, as of Release 6.40, you will receive a warning about the syntax check if you access identical components within a class declaration or a method with different descriptions.
ABAP_MODIFICATION_4 - Unused private components
As of Release 6.40, all unused private components of a class lead to a warning during the enhanced program check. Private methods must be called, private events must be both triggered and processed.
