Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse-dev] Compiler warnings

How about if you just perform a sweep before each Milestone build? (Maybe the Integration builds too but that might be too frequent.) And just encourage people to get rid of them at other times when it's convenient. That way you'd be unlikely to see many if any immediately prior to the release.

> -----Original Message-----
> From: Olivier Thomann [mailto:Olivier_Thomann@xxxxxxxxxx] 
> Sent: Tuesday, April 22, 2003 10:42 AM
> To: eclipse-dev@xxxxxxxxxxx
> Subject: [eclipse-dev] Compiler warnings
> Hi,
> I think it is time to change the settings of the compiler for 
> everyone. I
> noticed new warnings in the latest nightly builds. They are 
> mostly due to
> unused imports. It might be a godd thing that everyone is using the
> following settings:
> - unused import = ERROR
> - unused locals = ERROR
> - non static access to static member = ERROR
> - assignment has no effect = ERROR
> - Using a char array in string concatenation = ERROR
> This might help to reduce the number of useless warnings. It 
> took time to
> get rid of them prior to 2.1 release. So we might want to change the
> settings immediately and that should prevent us from chasing 
> them right
> before the next release.
> Any comment?
> Olivier
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx

Back to the top