I don't think there's any harm in putting StyleCop in the project at this
stage, but of course, no harm not putting it in either. It would be handy
for people who already have VS2008/2010, as we could keep Lucene with the
same style format across the project as a whole.
IMO, I think the Naming, M
>
> I don't think there's any harm in putting StyleCop in the project at this
> stage, but of course, no harm not putting it in either. It would be handy
> for people who already have VS2008/2010, as we could keep Lucene with the
> same style format across the project as a whole.
>
We should m
Agreed. StyleCop and FxCop are both quite handy and can only serve to
benefit the project.
-T
On Mon, Aug 1, 2011 at 10:39 AM, Prescott Nasser wrote:
>
>
>
>>
>> I don't think there's any harm in putting StyleCop in the project at this
>> stage, but of course, no harm not putting it in either. I
StyleCop by default adheres strictly to ms coding guidelines and then some.
http://blogs.msdn.com/b/brada/archive/2005/01/26/361363.aspx (even though a
deal of the internals of the framework breaks these rules).
You can turns rules off but if you want rules that differ from the default
ones, rule
The only problem with some modifying the code in this manor is it is going
to make it difficult to manually port from Java. Digy has talked about this
in the past and can provide more detail. The summary is that as the code
and comments diverge from the Java code it gets harder port Java patches.
