Re: [edt-dev] comments available in lexer

[bart.decuypere@xxxxxxxxxxx]

>>We want to implement something
along the lines of the Java annotation "@SuppressWarnings" without
impacting the EGL Syntax. 

>>We were thinking about doing this using JavaDoc like comments.

>>It turned out we could not do this without modifying the lexer,
since it ignores comments for the larger part. 




>Hi Bart 
>EGL has annotations similar to java annotations.  All EGL properties
are actually these annotations.  In EDT you can define your own.  Also,
processing these is probably better >handled through the files that
are persisted for each part.  In RBD these are the *.IR files.  In
EDT these would be either *.eglbin or *.eglxml files.  There is well
defined API for >loading and accessing these files.  From there
one can do all the code analyses you desire including accessing your annotations.
 To get help about how to use the API (there >is not much doc out
there except for the javadoc on the classes) you can post questions out
on edt-dev and i would expect someone from the community to answer (like
Assist, >Xact, IBM, etc).  It is best to have these conversations
out there.  Hope this helps. 

>Cheers 

>Tim W Wilson
>STSM Rational Developer Architecture & Development


Thanks Tim,

for your comment. However, we do  not think that
the current annotations are sufficient, because they can only be attached
to to specific parts (Records, Programs, DataItems, ...).

As our QA tool would check stuff on the level of single
statements/expressions, we would like to have something that is at least
applicable on the line level (such as a comment).  It would instruct
the QA tool to ignore the violation (starting) on the next line.

Another argument is that a comment is not intrusive, and
is not parsed by tools that are not aware of it. I think of the same level
of intrusiveness as XML processing instructions (<?myapp blahblah ?>)
which is basically ignored by other tools. Annotations have a higher level
of intrusiveness, they are parsed, validated...

Having comments returned by the lexer is still useful
for us.

I am looking forward to any further comments... 

Bart.





This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify KBC immediately and then delete this e-mail.
KBC does not accept liability for the correct and complete transmission of the information, nor for any delay or interruption of the transmission, nor for damages arising from the use of or reliance on the information.
All e-mail messages addressed to, received or sent by KBC or KBC employees are deemed to be professional in nature. Accordingly, the sender or recipient of these messages agrees that they may be read by other KBC employees than the official recipient or sender in order to ensure the continuity of work-related activities and allow supervision thereof.