Well, here's an unexpected initial result.
I just ran a build of langtools+jdk on my ubuntu laptop. I got a
whopping 2658 warnings!! [Those who volunteered to help get rid of
all the warnings, don't all step back at once!] But surprisingly,
after a quick "sort -u", only 625 of them are
Depending on what lint options you use, deprecation warnings are
typically reported as a single "Note:" at the end of the compilation,
rather than as individual warning messages. Ideally, they should go
too, but for now, I'd settle for removing messages that show up as
diagnostics in IDEs,
Just curious, would part of this revision process entail removing
calls to deprecated methods and replacing them with their documented
replacement methods?
There are many warnings about calls to deprecated methods in the
OpenJDK code.
Rob Ross, Lead Software Engineer
E! Networks
---
On Jul 11, 2008, at 10:00 AM, Thorbjørn Ravn Andersen wrote:
Jonathan Gibbons skrev den 11-07-2008 13:52:
Yes, that technique can work well. But either way, the next step is
to try writing the code to analyze the build log, to see how far
the general
idea can be taken, and how much interes
Jonathan Gibbons skrev den 11-07-2008 13:52:
Yes, that technique can work well. But either way, the next step is
to try writing the code to analyze the build log, to see how far the
general
idea can be taken, and how much interest there is to track/fix warnings.
Personally I'd like there to
On Jul 11, 2008, at 2:29 AM, Volker Simonis wrote:
On 7/10/08, Jonathan Gibbons <[EMAIL PROTECTED]> wrote:
The JDK build generates a whole lot of warnings along the way. This
is
bad because these warnings can sometimes mask real errors. For a
variety of reasons, it appears to be hard to try
On 7/10/08, Jonathan Gibbons <[EMAIL PROTECTED]> wrote:
> The JDK build generates a whole lot of warnings along the way. This is
> bad because these warnings can sometimes mask real errors. For a
> variety of reasons, it appears to be hard to try and get rid of all the
> warnings, so this messag
