I do not know about the license, but I assume it would be ok to use it on mono classes. Run the tool, and use common sense about the errors it reports. If in doubt ask on the list. For instance FXcop checks to see if a namespace has too many classes (should be split) or too few classes (should be combined). The real test of namespace size is does this stuff go together. Many of the .NET name spaces have too many or too few classes by FXCop standards. Of course we would not split or combine the namespaces. This is just one example. When working at the library or compiler level, this that might not make sense otherwise can still be good. Still FXCop is a good tool, and if it flags something as bad, it should at least be looked at. Dennis
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, February 03, 2003 9:42 AM To: [EMAIL PROTECTED] Subject: Mono-list digest, Vol 1 #761 - 8 msgs Message: 8 Date: Mon, 03 Feb 2003 18:41:55 +0100 From: Jeroen Janssen <[EMAIL PROTECTED]> To: mono-list <[EMAIL PROTECTED]> Subject: [Mono-list] FxCop? Hello, I recently saw Miguel mention FxCop. I'm not sure about the licensing stuff, so I'm asking here (hoping someone can answer this question): Is it allowed to use FxCop on the (mono) class libraries / assemblies and (based upon it's analysis) modify the mono sources? Or rephrasing: Are we allowed to use this tool to improve Mono? If the answer is yes, then how are we going to proceed with this? Do we agree with all the rules it checks, etc? Is it ok for me to run the tool on a certain assembly and start "fixing" things? --- Jeroen Janssen --__--__-- _______________________________________________ Mono-list mailing list [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list End of Mono-list Digest _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
