First of all. The problems view includes a nice filter:
A concerted effort would be something new for us. :-)
I'm working on http://objectstyle.org/jira/browse/WOL-298 for quite a
while. Most of the warnings belong to this task. You're welcome to
reduce the numbers. (I'm doing that whenever I have the time for
that. The deprecation stuff raised the number again.)
The settings are in the svn. Any comments?
Uli
Am 17.09.2006 um 18:39 schrieb Mike Schrag:
> The first step is probably to agree on what warning sets we care
> about and commit those preferences into SVN. For instance, if you
> turn on all warnings in Eclipse, there are some that you can't
> actually fix without breaking things (unusued variables and
> exceptions that are actually used by subclasses, for instance).
> But I agree with you, I'd like to pick the warnings we collectively
> think are important and knock them out. I did a pass on Project
> Wonder just this past weekend and it's so nice to have an empty
> warnings list.
>
> ms
>
> On Sep 17, 2006, at 12:11 PM, Pierre Frisch wrote:
>
>> Could we make a concerted effort to remove warnings when compiling
>> wolips there are over 300 warnings when building wolips and the
>> number is growing not diminishing!!! I really think we should try
>> to reduce that number to 0. This is annoying for me as I am trying
>> to work on wolips while having other projects open and I both sets
>> of warning mix. I have always believe that warning are important
>> and I have found over the year that fixing them pays big dividends
>> when you look for that hard to find bug.
>>
>> Yes I am ready to volunteer and do some of the work.
>>
>> Thank you for the good work
>>
>> Pierre
>
This archive was generated by hypermail 2.0.0 : Sun Sep 17 2006 - 14:04:52 EDT
