Closed webracer999 closed 1 year ago
I'm missing the reason why "RETURNING large tables is usually okay" (Clean ABAP). The reason in my eyes is ABAPs "Sharing Between Dynamic Data Objects" (https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abenmemory_consumption_3.htm). So internal tables aren't copied in memory, when they don't differ.
Returning of large tables therefore effectively end in a logical "call by reference". Which can be observed with the debugger.
yea, also see https://blogs.sap.com/2017/07/30/the-mysteries-of-the-returning-parameter/
That's correct, the reason being the copy-on-write mechanic with respect to the table data should be mentioned.
I'm missing the reason why "RETURNING large tables is usually okay" (Clean ABAP). The reason in my eyes is ABAPs "Sharing Between Dynamic Data Objects" (https://help.sap.com/doc/abapdocu_750_index_htm/7.50/en-US/abenmemory_consumption_3.htm). So internal tables aren't copied in memory, when they don't differ.
Returning of large tables therefore effectively end in a logical "call by reference". Which can be observed with the debugger.