[MonoDevelop] Code analysis soc project

Mike Krüger mkrueger at novell.com
Thu Mar 25 03:12:46 EDT 2010


Hi

> I have become quite familiar with the new DOM. I have partially
> implemented a rule for CS5001 (source file must have Main) and
> checking functions for invalid returns  http://pastebin.com/zPnNwvs3
> Again these are POCs, I had to do an ugly hack to workaround the non
> availability of getting the ReturnType of a method. There are similar
> problems getting their arguments as well.
> 

Return types should work now. When you don't get certain information in
an AST node per property the best place to look at is the CSharpParser
that is the 'documentation' for which role the children are added to
that node and then it's easy to change the property to use the correct
rule or add the missing property.
(I take patches :)) 

> The new DOM is quite familiar to me now. I think this would be a good
> project because not only will it allow me to create a useful tool, but
> it can provide a good test case and feedback regarding the new DOM.
> Also, I plan to refactor the metrics addin to use the new DOM as soon
> as it becomes 100% stable.
> 

I can need any feedback I can get for this new one. In this state
changes to the DOM are very easy. It's quite similiar to the NRefactory
DOM therefore the transition to the new one should be straightforward.
It should be more usable like an attributed NRefactory DOM than a
complete new one. (at least in 90% of the cases, there are small
differences because the NRefactory DOM needed to match VB.NET as well) 

Regards
Mike 



More information about the Monodevelop-list mailing list