2012/7/20 Björn Pollex <[email protected]>: > Is there already an existing practice?
Not really. My personal practice is to fix all warnings whenever I modify an existing source. > My suggestion would be to annotate warnings that are intentionally ignored > with > @SupressWarnings, and try to fix the rest. If no one objects, I would also > mention this in the coding guideline. I'd reverse the priorities: Fix the warning, and if nothing else helps (e.g. for unchecked cast on pre-generic APIs) use @SuppressWarnings. Cheers, Harald _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
