You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@netbeans.apache.org by Peter Nabbefeld <pe...@gmx.de> on 2018/12/01 06:12:03 UTC
Re: Java Syntax checking problem/bug
I got similar problems with different versions of NetBeans, and I cannot
tell which are the preconditions for this bug. The files are marked wit
a red bulb in the project tree, so parsing obviously detects the errors,
but for some reason sometimes error highlighting stops for the active file.
From the behavior, I'd guess highlighting is switched off during
typing, but NetBeans fails to re-enable it when typing stops. Just a
guess, don't know really.
Kind regards
Peter
Am 29.11.18 um 21:49 schrieb Emilian Bold:
> Interesting. Can you provide a short(er) java file where this bug
> reproduces?
>
> It might be a nb-javac parser bug or something in the classes built on
> top of that.
>
> Does it happen if you change the variable names (x1, x2, y1, y2, etc)?
> If it's for the same variable name then maybe some hash collision
>
> Can you reproduce this on NetBeans 9 (with, without the nb-javac from
> Oracle?).
>
> --emi
>
> http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
>
>
> On Thu, Nov 29, 2018 at 6:52 PM Joseph Huber <JHuber@stanref.com
> <ma...@stanref.com>> wrote:
>
> Hello!
>
> Please see the screenshots below (hopefully they come through on
> the mailing list). I am working with Netbeans 8.2 in Windows 10.
> The variable “x1” is not defined, but Netbeans stops showing the
> hint identifying it as a problem after it encounters a particular
> statement. “x1” is italicized, but no lightbulb in the margin or
> red underscore. The scope of the problem is not limited to the
> shown method. The “cannot find symbol” hint stops working for the
> remainder of the file, although other syntax errors are found, and
> other hints seem to be working fine in the remainder of the file.
>
> Now, commenting out a couple of statements, things work for a
> little while longer.
>
> Commenting out another statement fixes the problem for the rest of
> the file. There are nearly 1000 lines of code after this code
> fragment, and the “cannot find symbol” checking works fine for the
> rest of the file after this last statement is commented out.
>
> dptc1 is another DxProTopComponent defined at the class level,
> jpIB1 is a JPanel, and jcbModelFam is a JComboBox.
>
> This is mostly an annoyance, in that if I make a typo, it crashes
> during debug or build, rather than being identified in the editor.
>
> Any thoughts on what might be going on?
>
> Thank You!
>
> Joe Huber
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: users-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@netbeans.apache.org
For additional commands, e-mail: users-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists