Michael, >> Michael Descher wrote : >> I like the idea of code analysis though I think this is a complex area >> which probably is not so easy to implement. I fear a little that the results >> of such a "non-human" code analysis won't be too impressive.
As the code is already parsed by IDEA, I suspect that "looking for some smell patterns should be pretty simple. I'd suggest we start simply, and chose the features with the highest ROI : *********************************************************************** very simple to implement <- and -> interesting, but difficult to do by hand *********************************************************************** The size related smells : 1� "Too much code": - find the classes too big (ex. LOC > 2000 ) - find the methods too big (ex. LOC > 2000 ) - find the classes with too many methods - find the classes with too many public members ... 2� "Too few code": (look at http://www.c2.com/cgi/wiki?CodeSmells) 3� "Find the dead code" Why maintain code that is never used. Number 1 in my list. Requested by many, often. 4� Stupid looking names no vowels : String ptrkpppzz = ... too short : int pe = ... too long with same case : boolean thisiscryingforabettercasing = false ; ... 5� find duplicate code. I installed same (http://sourceforge.net/projects/same/) as an external tool. It's simple, free, written in java, the code is available... It would be more useful if it were integrated in IDEA : messages would include live pointes to the line xxx in the code. .... I only chose the basic ones, that could be added in a day (at least 1,2 and 4) If was fine for IDEA to start as a super smart editor, but it's not enough. I want more. Sorry guys, but you spoiled me by showing what you could do. Alain Ravet This mail has been checked by exiscan. To be safe, please scan the mail attachements with your local virus scanner ! _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
