Bug 252487 [DataBinding] use Double.isNaN(d) instead of d!=d to check for NaN
There are two warnings in StringToNumberParser related to the fact that we use "doubleValue == doubleValue" to determine whether the value is NaN (suprisingly, NaN is never == NaN, even if it is the same variable). We should be using Double.isNaN(doubleValue) instead.
bundles/org.eclipse.core.databinding/src/org/eclipse/core/internal/databinding/conversion/StringToNumberParser.java
.getErrorIndex() : position.getIndex();
		if (errorIndex < value.length()) {
			return BindingMessages.formatString(BindingMessages.VALIDATE_NUMBER_PARSE_ERROR,
					new Object[] { value, new Integer(errorIndex + 1),
							new Character(value.charAt(errorIndex)) });
		}
		return BindingMessages.formatString(BindingMessages.VALIDATE_NUMBER_PARSE_ERROR_NO_CHARACTER,
				new Object[] { value, new Integer(errorIndex + 1) });
	}
	/**
	 * Formats an appropriate message for an out of range error.
	 *
	 * @param minValue
	 * @param maxValue
	 * @param numberFormat when accessed method synchronizes on instance
	 * @return message
	 */
	public static String createOutOfRangeMessage(Number minValue,
			Number maxValue, NumberFormat numberFormat) {
		String min = null;
		String max = null;
		synchronized (numberFormat) {
			min = numberFormat.format(minValue);
			max = numberFormat.format(maxValue);
		}
		return BindingMessages.formatString(
				"Validate_NumberOutOfRangeError", new Object[] { min, max }); 
	}
	/**
	 * Returns <code>true</code> if the provided <code>number</code> is in