Why does ABAP divide classes into implementation and definition?

I know that ABAP objects are of some old nature, but as far as I know, you still have to use at least two "sections" to create a complete class.

ABAP:

CLASS CL_MYCLASS DEFINITION.
    PUBLIC SECTION.
        ...
    PROTECTED SECTION.
        ...
    PRIVATE SECTION.
        ...
ENDCLASS.

CLASS CL_MYCLASS IMPLEMENTATION.
    ...
ENDCLASS.

Java:

public class MyClass {

    <visibility> <definition> {
        <implementation>
    }

}

Wouldn't it simplify / speed up development if it were combined like most modern languages?

What are the reasons for this separation?

+4
source share
2 answers

/ (), : , , , . ABAP - , : Pascal , Object Pascal . , ++ ​​ , -.

+3

, :

(?) , SE24. dynpro .

, . .

0

All Articles