eclipse warnings

[John Hendrikx]

IMHO, there is no capacity for this.

I did many warning fixes, and there are PR's outstanding with warning 
fixes, but they're not getting reviewed.

There are other PR's outstanding that are more valuable, but are not 
getting reviewed.

I feel we need to fix that first before we can endulge in warning fixes.

As for the potential null pointer access, it's often a false positive; 
static analyzers have a hard time determining if a loop is entered at 
least once (or an if in that loop) and so will warn that a local can 
maybe be null if it was initalized inside a loop.

--John

On 04/12/2023 17:34, Andy Goryachev wrote:
>
> Dear colleagues:
>
> Imported the openjfx project into another workspace with a more 
> stringent error checking and discovered a few issues:
>
>   * potential null pointer access: 295
>   * unnecessary cast or instanceof: 190
>   * redundant null check: 61
>
> Do we want to clean these up?
>
> -andy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20231205/d91349bc/attachment-0001.htm>