Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » Question about analysis rules: J2SE Best Practices
Question about analysis rules: J2SE Best Practices [message #80231] Wed, 09 August 2006 11:41 Go to next message
Thorsten  Möller is currently offline Thorsten MöllerFriend
Messages: 25
Registered: July 2009
Junior Member
Hello,

today I tried TPTP for the first time and it is a really impressive tool.
During my first tests I tried to analyse some code against the "J2SE Best
Practices" rules. There are a lot of checks, for instance "Avoid using
"this" as a lock in synchronized statements". However, I was wondering
whether there is some explanation/documentation associated to each rule
available which would tell me the reason why certain code might produce
problems, for instance why shouldn't "this" be used as the lock in
synchronized blocks. Ok, some of the rules really don't need further
explanation since they are really self explaining like "Avoid casting
primitive types to lower precision". But there are a lot of rules where I
have would have to search in whatever external documents to find
explanations about the reason. So I would really appreciate a function which
associates a description/explanation to each rule giving more details about
the rules.

Regards,
Thorsten
Re: Question about analysis rules: J2SE Best Practices [message #81220 is a reply to message #80231] Sun, 20 August 2006 10:20 Go to previous message
Eclipse UserFriend
Originally posted by: omarquez.uwaterloo.ca

Thorsten Möller wrote:
> Hello,
>
> today I tried TPTP for the first time and it is a really impressive tool.
> During my first tests I tried to analyse some code against the "J2SE Best
> Practices" rules. There are a lot of checks, for instance "Avoid using
> "this" as a lock in synchronized statements". However, I was wondering
> whether there is some explanation/documentation associated to each rule
> available which would tell me the reason why certain code might produce
> problems, for instance why shouldn't "this" be used as the lock in
> synchronized blocks. Ok, some of the rules really don't need further
> explanation since they are really self explaining like "Avoid casting
> primitive types to lower precision". But there are a lot of rules where I
> have would have to search in whatever external documents to find
> explanations about the reason. So I would really appreciate a function which
> associates a description/explanation to each rule giving more details about
> the rules.
>
> Regards,
> Thorsten
>
>

To give such documentation, the TPTP Analysis framework uses the Dynamic
Help feature that Eclipse provides. Simply press F1 when you select the
rule in the Analysis Launch Dialog and you will see a paragraph of
explanation with links to Examples and Solutions

best regards,

--
Orlando Marquez
University of Waterloo
Previous Topic:No Line Coverage Icon on Package View
Next Topic:NPE when launching test with Line Coverage enabled
Goto Forum:
  


Current Time: Thu Apr 25 17:24:36 GMT 2024

Powered by FUDForum. Page generated in 0.02626 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top