[cdt-dev] Re: Coding standards enforcer in CDT...

[Randy D.Smith <randy.d.smith@xxxxxxxxx>]

Monali A. Bhalerao <MonaliB@...> writes:

> Hi Srikanth!
> 
> 1. Enforce customized coding standards
>    We have plans to integrate the "LINT" tool with a feature to add
> customized rules but nothing planned on code beautification.
> ...
> 
> Best Regards,
> Monali
> 

I know some of you guys that have run into me at EclipseCon (and CDT F2F
afterwards) are tired of me beating the same drum, but...

1. is a great place to utilize TPTP's Static Analysis tool instead. It currently
has two rules, so there's plenty of opportunity to write rules for it that will
tag (and potentially allow quick-fix) for your very own set of customized coding
standards. It's a solution in the Eclipse chain just waiting to be used in
situations like this.

Check out the tutorials at <
http://www.eclipse.org/tptp/home/documents/process/development/static_analysis/TPTP_static_analysis_tutorial_part1.html
> and <
http://www.eclipse.org/tptp/home/documents/process/development/static_analysis/TPTP_static_analysis_tutorial_part2.html
>, and give it a try. The Java rules (70 of them) exist in the Callisto release
(the tutorial will tell you how to set the Preferences to turn the Analysis
toolbar item on), but you'll have to download the "C++ rules Technology Preview"
from the TPTP download site and install that plugin to get the current TWO
(count them, *2*) rules for C++.

I'm sure Steve Gutz (the IBM guy who did this TPTP feature) would love to see
more internal adoption of this, and additional rules written for C++. (I've
spent a bit of time at the CDT F2F trying to get the Photran guys to look at
this as well, and I think they're intent on getting Fortran support sooner!
Nothing like a little competition to really get things going! :-) )
--
     RDS

Randy D. Smith            randy (dot) d (dot) smith (at) intel (dot) com
Eclipse TPTP Committer, Platform Proj (data collection/agent controller)