Bug 107547 [5.0] autoboxing syntax coloring fails with signed primitive value
AS IS: with 3.1.1 M20050811-0400, followed code fragment have different coloring on the auto-boxed int value, if the value has + or - sign before (in the preferences for auto-boxing: the boxed values should be bold and red). TO BE: both occurencies of value in put(..., +-value) should be colored in the same color as the first case. Example: TreeMap<String, Number> summary = new TreeMap<String, Number>(); int value = 0; summary.put("key", value); // value is shown in bold and red color - OK summary.put("key", -value); // value has usual font properties - NOK summary.put("key", +value); // value has usual font properties - NOK
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightings.java
return false;
		}
		/*
		 * @see org.eclipse.jdt.internal.ui.javaeditor.ISemanticHighlighting#getDisplayName()
		 */
		public String getDisplayName() {
			return JavaEditorMessages.SemanticHighlighting_abstractMethodInvocation;
		}
		/*
		 * @see org.eclipse.jdt.internal.ui.javaeditor.ISemanticHighlighting#isMatched(org.eclipse.jdt.core.dom.ASTNode)
		 */
		public boolean consumes(SemanticToken token) {
			SimpleName node= token.getNode();
			if (node.isDeclaration())
				return false;
			IBinding binding= token.getBinding();
			boolean isAbstractMethod= binding != null && binding.getKind() == IBinding.METHOD && (binding.getModifiers() & Modifier.ABSTRACT) == Modifier.ABSTRACT;
			if (!isAbstractMethod)
				return false;
			
			ITypeBinding declaringType= ((IMethodBinding)binding).getDeclaringClass();
			if (declaringType.isAnnotation())
				return false;
			return true;
		}
	}
	/**
	 * Semantic highlighting for inherited method invocations.
	 */
	private static final class InheritedMethodInvocationHighlighting extends SemanticHighlighting {