Description Olivier Thomann 2005-10-06 13:43:59 EDT

Following of bug 111703, we should improve error highlighting for static
initializer. We are underlining the whole static initializer. I suggest to
highlight only the opening brace.

For example, on the test case from bug 111703, we now report:
----------
1. ERROR in D:\tests_sources\X.java
 (at line 27)
	static {
                      myTree.addTreeSelectionListener(list);
                      }
	      
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cannot define static initializer in inner type new ActionListener(){}
----------
2. ERROR in D:\tests_sources\X.java
 (at line 28)
	myTree.addTreeSelectionListener(list);
	^^^^^^
Cannot make a static reference to the non-static field myTree
----------
2 problems (2 errors)

I suggest:
----------
1. ERROR in D:\tests_sources\X.java
 (at line 27)
	static {
	       ^
Cannot define static initializer in inner type new ActionListener(){}
----------
2. ERROR in D:\tests_sources\X.java
 (at line 28)
	myTree.addTreeSelectionListener(list);
	^^^^^^
Cannot make a static reference to the non-static field myTree
----------
2 problems (2 errors)

This would help the user to locate the error without the whole body of the
static initializer or I could start the highlighting on the static keyword, but
this could lead to the same issue in case of javadoc comment before the static
initializer.