News
UseIsOperatorRule
On Mono-dev, Juraj Skripsky posted a patch to cleanup "as" casts.
(CC'ing him...)
[link]
One of the cleanup is this (there were 3 of them in Mono corlib):
- return value as EncoderExceptionFallback != null;
return (value is EncoderExceptionFallback);
Re: ProtectionTooPermissiveRule
Hello Vlad,
Yes. Currently no Gendarme runner support a concept of "assembly
group" (or solution), but this is something we discussed because it
affects some existing rules (like some smells). Without this concept
it's
Re: PropertySetterNotNeededRule
Hello Vlad,
hmm... I'm not sure I totally understand ? by "possible" do you mean
"useful in a specific solution you work with" or something else ?
It could be helpful to supply test cases. For example what you
PropertySetterNotNeededRule
Given public properties can be accessed from anywhere, this is another
difficult rule to consider. But I maintain that I work in a Solution
with definite scope constraints that should make this sort of rule
possible.
Thanks,
Vlad
ProtectionTooPermissiveRule
I would like to increase the protection wherever possible to private
if possible i.e. a rule that identifies all Methods, properties, even
variables and anything else applicable that are declared with too
generous a protection level.
I understand that for libraries that expose functionality, it is
Re: [gendarme] Re: Gendarme.Framework.Rocks
I got a preview patch :) Apply it and type make doc. This will
generate a new directory called doc, and then you could see the
documentation typing: monodoc --edit doc
With the patch we will regenerate completely the documentation
Re: Gendarme.Framework.Rocks
Hola Nestor!
That would be very nice :) and make it easier for people using
MonoDevelop to write/test rules.
Yes, this is probably the best way to do it - except JB will be
looking, with good reasons I admit, for symmetry ;-)
E.g. providing IsGetter without IsSetter would be "bad" (even if only
Re: [gendarme] Gendarme.Framework.Rocks
Hello Sebastien.
Yes, in this case IMHO the size matters. I have seen your new rules
(AvoidEmptyInterfaces, AvoidPropertiesWithoutGetAcces sor ...) and I like
the new code.
This could be linked with the monodoc task, and I have
Gendarme.Framework.Rocks
Hello everyone,
Following (but not totally blindly ;-) JB Evain, of Cecil-fame, newest
project Mono.Rocks [1] and some discussions at the last Mono summit,
Gendarme's first rocks are now in SVN (and some people, besides me
Re: [gendarme] Re: RFC - changing I[Assembly|Module|Type|Method||]Rule interfaces
You have reason, I haven't thought in implement more than one
interface. Good catch!
Yes, really we haven't a need for changing the names.
Néstor.