[MonoDevelop] Code analysis soc project

Mike Krüger mkrueger at novell.com
Tue Mar 23 02:18:37 EDT 2010


Hi
> Apparently the current
> version of NRefactory is not good enough to detect certain types of
> semantic errors. Hence detecting errors such as invalid return types,
> incorrect parameters and so on are very difficult to do with the
> current NRefactory. 

These two are possible :) (but anything that needs some more analyzation
than a resolve + type check is painful to implement)

> This is because there is presently no way to go to
> the parent of the node you've no way to go to the parent and top-down
> analysis is difficult because "<mkrueger>: because you can't go to the
> children of the nodes without knowing the type of the node". Some
> things that can be implemented however are naming conventions,
> spellings in comments and string literals and so on. Given this
> backdrop is there any point proceeding with this project? Or should
> one wait for the new DOM to be completed?

The new dom currently is almost ready - if you want to work with that
it's possible. You just need a customized mono compiler source code &
comment out the parser file.

> 1) Extending the Code metrics addin: The addin i posted on the mailing
> list does quite a few things, but a lot is still left to implement,
> such as cohesion, coupling and association between classes. Maybe I
> can add a few more metrics such as
> http://yunus.hacettepe.edu.tr/~sencer/oom.html
> But the killer feature would be CQL, which allows one to query the
> code base for types, methods and namespaces that satisfy criteria as
> specified in a very SQL type language. NDepend implements CQL and I
> will be trying to replicate that.
> 

This seems to be a good project :)

Regards
Mike



More information about the Monodevelop-list mailing list