On Feb 26, 6:18 pm, Reinier Zwitserloot <[email protected]> wrote: > Nobody is talking about forcing anything. @SuppressWarnings exists for > a reason. The compiler is there to tell you there's a problem you > should look at, and when you've looked at it, you can easily tell the > compiler to shut up henceforth. At least, that's the idea.
Yeah, I understand - but that's the point I made about showering developers writing questionable code with warnings by default using Jikes as an example - they'll find it easier to turn them off, then to go and fix them. ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
