https://bugzilla.novell.com/show_bug.cgi?id=666400
https://bugzilla.novell.com/show_bug.cgi?id=666400#c3 --- Comment #3 from Sebastien Pouliot <[email protected]> 2011-01-23 16:24:10 UTC --- So all methods, getters/setters, included are part of the rule logic which is generally the case in (?all?) such algorithms. That's problematic since the algorithms generally promotes the "all methods use all fields" as being the uber-cohesive goal since IMO it defeat the most common use of properties. Now there is, at least in C# 3, an easy way to distinguish "simple" and "complex" properties by using "automatic properties" - just like your sample does :-) I'll update the rule to ignore them (getters/setters and backing fields are all marked as compiler generated). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
