documentation error for the obsolete CALL METHOD form, about method chaining ?

Sandra_Rossi — Wed, 23 Jan 2019 17:57:29 GMT

Hello,

In this page of the documentation about obsolete CALL METHOD variants, we see:

CALL METHOD { static_meth( ) 
 | static_meth( a ) 
 | static_meth( p1 = a1 p2 = a2 ... ) 
 | static_meth(  ) }. 

CALL METHOD static_meth .

...

If CALL METHOD is used for the standalone method call, no chained method
calls are possible and the operators NEW and CAST cannot be used to specify the method.

(note: "standalone method call" is the name for "static_meth")

I think that "If CALL METHOD is used for the standalone method call, no chained method calls are possible ..."

is missing a "NOT". The right sentence should be :

"If CALL METHOD is not used for the standalone method call, no chained method calls are possible ..."

This question was asked in stackoverflow by someone else: https://stackoverflow.com/questions/54329867/abap-call-method-and-method-chaining

What do you think?

Thanks!

Sandra

Adding horst.keller in the loop...

Re: documentation error for the obsolete CALL METHOD form, about method chaining ?

Sandra_Rossi — Sat, 23 Feb 2019 16:48:22 GMT

I close the question because there was an answer in stackoverflow : "the docu team [...] answered that it has already been reported and they corrected it in the latest version."

Old statement:

"If CALL METHOD is used for the standalone method call, no chained method calls are possible and the operators NEW and CAST cannot be used to specify the method."

New statement according to stackoverflow's answer:

"With the second variant without round brackets, chained method calls are not possible and the operators NEW and CAST cannot be used."

topic documentation error for the obsolete CALL METHOD form, about method chaining ? in Application Development and Automation Discussions

documentation error for the obsolete CALL METHOD form, about method chaining ?

Re: documentation error for the obsolete CALL METHOD form, about method chaining ?