5 Comments

• 
  Kesari

  # February 20th, 2013 at 11:05 pm

  Hi Naimesh,

  While enhancing our automatic code review and rework tool (a.k.a smartDevelop ) we found below observations, thought, with your permission, i would take an opportunity to add as a comment to your post.

  The prgama’s are treated as PART of the ABAP code line and are not comments ( Unlike the Pseudo Comments ). i.e pragma is mentioned before the ‘.’ ,the abaps end of statement indicator.

  In addition to the sample program given by SAP, ABAP_SLIN_PRAGMAS, there is an addon table TRPRAGMA, where we have additional pragmas which form an extension to the compilers list.

  There is only a “warning” message shown if a developer uses a non existent pragma by any chance.

  A non existent just-like-that pragma

   
  ##Just-like-that Data: w_data TYPE   bseg .
   

  Pragmas can be parameterised with [ ] addition, And here Pragma parts can not be separated by space ( See the example program “Demo_read_table_using_key” ).

  If there are multiple pragmas to be applied in a single code statement , then the code should be spread into multiple lines, and respective pragma has to be mentioned besides each ‘sensitive’ token of the statement.

   
  " The below line would give an error : 
  Data: w_data3 like ##Just-like-that  bseg  ##Just-like-that.
  *
  "So it has to be broken into 2 lines
  Data: w_data3 TYPE  ##Just-like-that
                bseg  ##Just-like-that.
   

  Pragmas can hide WARNINGS and some specific errors also. Below is an example :

  Parameterised Pragmas and Hiding a syntax error with Pragma

   
   itab TYPE STANDARD TABLE
                       OF i
                       WITH NON-UNIQUE    KEY primary_key
                         COMPONENTS table_line
                       WITH UNIQUE SORTED KEY sorted_key
                         COMPONENTS table_line
                       WITH UNIQUE HASHED KEY hashed_key
                         COMPONENTS table_line
                       ##tabkey[hashed_key][sorted_key].
   

  Some of the frequently used pragmas :

  ##FM_SUBRC_OK ( During exception handling of Function Modules )
  ##CALLED ( In case of dynamically called MODULE or SUBROUTINE definition)
  ##NEEDED (In case of a un used data declaration )
  ##too_many_itab_fields ( When the database table structure is a subset of the internal table)
  ##catch_all ( In case of Generalised class exception CX_ROOT is used with CATCH )
  ##no_text ( HardCoded texts)
  ##no_handler ( In case the CATCH statement doesnt pass the object reference into a declared object )

  Regards
  Kesari Katakam

• 
  Steve Oldner

  # February 21st, 2013 at 5:50 am

  We have used pseudo comments in custom programs since 7.0 and it is part of the ‘boiler plate’ ALV we use to create new ones. I haven’t seem pragmas yet.

  Thanks to both of you!!

• 
  Steve Oldner

  # February 21st, 2013 at 5:57 am

  I keep getting the “Welcome, you seem new here” toolbar. I follow you on Twitter and am subscribed to the blog.

• 
  Naimesh Patel

  # February 21st, 2013 at 8:51 am

  Hello Kesari,

  Thank you very much providing your real-time learning. Much appreciated. I now know how we can use the parameters to the Pragma to control the error or warning suppression.

  Regards,
  Naimesh Patel

• 
  Naimesh Patel

  # February 21st, 2013 at 8:56 am

  Hello Steve,

  Yes, pseudo comments are used widely to suppress many errors/warnings from SLIN execution. I’m sure you would start using pragma whenever it would be available to your system 😉

  RE Welcome.. new toolbar, I use Google Analytics to determine if the reader is new vs returning. I bet you are returning and participating reader. I guess the logic of Google Analytics doesn’t work as expected. I would try to fix it. Thanks for bringing to my notice.

  Regards,
  Naimesh Patel