Lars Hvam

If there is a class `CL_CUSTOMER` and `CL_ORDER` both implementing `IF_LOCKABLE`, then there is a possibility that these are handled by the same "lock manager" which casts the objects to...

`NEW zcl_bar( )->interface_method( ).`, yea, its convenient, but I'd argue that its not proper object oriented if the interface_method can be accessed outside a interface reference naming, yea, but the...

yea, well, yea, well if `itab` is empty, it can be argued that it is an optional branch? I'm not really sure what the abap style guide considers optional something...

yea, that makes sense but then the name "Don't declare inline in optional branches" is misleading, it should be "Dont use inline in unrelated branches" or something

anyhow, for now, just disable the rule, it might be changed completely, or renamed/decommissioned as the style guide is misleading

INTO TABLE

I'll add the good and bad example in the documentation, just have not gotten around to it

I've added, ```abap * Bad example SELECT field1, field2 FROM table INTO @DATA(structure) UP TO 1 ROWS ORDER BY field3 DESCENDING. ENDSELECT. * Good example SELECT field1, field2 FROM table...

thanks, its currently marked as "experimental", the small icon. Hmm, perhaps I should make it better vissible. It will eventually work, hopefully :) anyhow another test case to add 

keep it open please, I'll add this scenario as a unit test, when I get back to fixing/implementing the rule