Get Example source ABAP code based on a different SAP table
Compiler in ABAP Release 6.10 ITOC
ABAP_MODIFICATION_NN Error Handling Using the StatementSYNTAX-CHECK
The statement SYNTAX-CHECK has been enhanced so that the syntax check also continues after error messages occur, as long as the parameter ID = ERR is set. Any error messages are written to an internal table, which can be specified using TABLE. The collected errors also provide the return code sy-subrc = 4.
ABAP_MODIFICATION_NN Static Checks in Specified Offsets/Lengths
Previously, in offsets/lengths specified as field+offset(length) the values were not checked for convertibility to numbers of the types I, F, or P until runtime. This is now checked as part of the syntax check.
ABAP_MODIFICATION_NN Data Types for Source Code in SCAN ABAP-SOURCE
The statement SCAN ABAP-SOURCE has been enhanced so that fields of type C or string are allowed in the scanned source code, instead of an internal table. This means that an internal table no longer needs to be edited.
ABAP_MODIFICATION_NN Implementation in TOP Includes
If implementations of the type FORM, FUNCTION, or CLASS ... IMPLEMENTATION are made in a top include, a syntax warning is now produced. The program can still be activated however.
ABAP_MODIFICATION_NN Faster Generation of Program Segments
Program segments can be generated much more quickly, now that pre-compiled headers have been introduced. Pre-compiled headers allow the system to import and reuse previously processed data declarations of global classes, interfaces, and type pools more quickly, both during the syntax check and when generating the program. This means it is no longer necessary to import program segments repeatedly. If the compiler does not find a pre-compiled header for the required program segment, it generates one and stores it in the program buffer ( PXA). The addition WITH PRECOMPILED HEADERS of the statement GENERATE REPORT can now be used to speed up generation from within an ABAP program.
ABAP_MODIFICATION_NN Generating Data and Types in System Includes
Data and types in includes of the form < ...> were previously viewed as system objects and packed into a separate name space; however, this was ignored when the program was generated. For this reason, objects of this type could be hidden by global program definitions, so that it was unclear at runtime which definition was used. Now both generation and runtime handle system objects in the same way. Therefore in future, the following example will always produce the value 5. include < SCREEN>. data SCREEN type I value 5. write / SCREEN.
ABAP_MODIFICATION_NN Converting C Literals with a Negative Maximum Value
Previously, if an attempt was made to assign the highest negative integer value to a type I variable, in the form of the C literal '-2147483648', the system raised a catchable exception, CX_SY_CONVERSION_OVERFLOW. On the other hand, an assignment in the form of a numeric literal was accepted. Now both forms are supported, as the following example shows: ABEXA 01150
In the editing status of the dictionary, it is possible to set a DDIC database view to read only, so that ABAP programs cannot make any changes. Previously the editing status was only checked at runtime. Now a syntax error is produced when this situation is known statically.
ABAP_MODIFICATION_NN Passing the Source Code in GENERATE SUBROUTINE POOL
In the statement GENERATE SUBROUTINE POOL , source code can now also be passed in an internal table of line type string.
