Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cl_oo_abap_doc_reader, reading source code of class/intf #160

Closed
larshp opened this issue Aug 8, 2022 · 3 comments
Closed

cl_oo_abap_doc_reader, reading source code of class/intf #160

larshp opened this issue Aug 8, 2022 · 3 comments
Assignees

Comments

@larshp
Copy link
Collaborator

larshp commented Aug 8, 2022

zcl_aff_abap_doc_reader takes the source as input in create_instance

cl_oo_abap_doc_reader takes the name of the class/interface as input

to glue it together, we should read the source code, but which method is preferred to read class and intf source code? CL_OO_CLIF_SOURCE ?

@schneidermic0
Copy link
Contributor

schneidermic0 commented Aug 9, 2022

which method is preferred to read class and intf source code? CL_OO_CLIF_SOURCE ?

Yes, I suggest to use if_oo_clif_source as interface. You'll get an instance by calling cl_oo_factory=>create_clif_source( ). Actually, (as of today) it will return an instance of cl_oo_clif_source. ;)

@larshp
Copy link
Collaborator Author

larshp commented Aug 9, 2022

ok, so something like this?

DATA(ref) = cl_oo_factory=>create_instance( )->create_clif_source( 'CL_GUI_FRONTEND_SERVICES' ).
ref->get_source( IMPORTING source = DATA(sovs) ).
BREAK-POINT.

@schneidermic0
Copy link
Contributor

Yes, this is fine... except the BREAK-POINT statement :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants