I would like to take a leaf out of BOPF's book. The constant interfaces end with _C e.g., /BOBF/IF_DEMO_SALES_ORDER_C.
But as Matt mentioned, as long as the name is meaningful i wouldn't scratch my head over it 🙂
matthew.billingham:
"... the constant interface pattern describes the use of an interface solely to define constants, and having classes implement that interface in order to achieve convenient syntactic access to those constants"
In ABAP we don't need to do this, do we?
You have said & i quote, "can cause dependencies where you really don't want them." Can you give an example of this?
INTERFACE lif_shirt_sizes.
TYPES:
BEGIN OF ENUM size STRUCTURE mc_size,
s,
m,
l,
xl,
xxl,
END OF ENUM size STRUCTURE mc_size. " ENUM size
ENDINTERFACE.
CLASS lcl_demo DEFINITION CREATE PRIVATE.
PUBLIC SECTION.
CLASS-METHODS:
main.
PROTECTED SECTION.
PRIVATE SECTION.
ENDCLASS.
CLASS lcl_demo IMPLEMENTATION.
METHOD main.
DATA: size TYPE lif_shirt_sizes=>size.
cl_demo_input=>request(
EXPORTING
text = |Shirt Size|
CHANGING
field = size
).
cl_demo_output=>display(
SWITCH string( size
WHEN lif_shirt_sizes=>mc_size-s
THEN |Small|
WHEN lif_shirt_sizes=>mc_size-m
THEN |Medium|
WHEN lif_shirt_sizes=>mc_size-l
THEN |Large|
WHEN lif_shirt_sizes=>mc_size-xl
THEN |Larger|
WHEN lif_shirt_sizes=>mc_size-xxl
THEN |Largest|
ELSE |Invalid size|
)
).
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
lcl_demo=>main( ).
joao.sousa2
In what situations would the interface consumer require "constants"? -> As a consumer of the "constant" interface i need to know the acceptable shirt-sizes (in this case the enumerated type SIZE).
Of course, i can define the enumeration in an abstract class as well. But i am failing to see the advantage of it. Maybe someone clarify
BR,
Suhas
Bluesky
