Summary: | Inexact match searching in java.math.BigDecimal | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.1 | ||
Target Milestone: | 2.1 RC2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Jerome Lanneluc
2003-02-28 06:29:30 EST
declarationEnd of the constructor BigDecimal(String) is wrong: it points to the end of the file. BigDecimal(String) contains an assert statement and I was running in 1.3 compliance mode. Shouldn't the recovery handle this case? The inexact match is actually in the constructor that uses the assert statement. So it is expected in 1.3 compliance mode. Closing. |