Bugzilla – Full Text Bug Listing
| Summary: | [1.5][search] fails to find call sites for varargs constructors | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Robert M. Fuhrer <rfuhrer> |
| Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | markus.kell.r |
| Version: | 3.1 | ||
| Target Milestone: | 3.1 M5 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
*** This bug has been marked as a duplicate of 84100 *** Oops, that was too fast. This bug is not a dup of bug 84100. This one is for vararg _constructors_ (the other one is for methods). ConstructorLocator should not compare constructor arguments number when last one is vararg... Fixed. Search engine now find constructors with varargs parameter references. [jdt-core-internal] Change done in ConstructorLocator#match(*, MatchingNodeSet) methods. Test cases added in javaSearchBugsTests Verified in I20050215-2300 |
The search engine fails to find the call to the varargs constructor in the example below. Simply highlight the constructor's name and invoke "References" - > "Workspace" from the Java editor context menu; no occurrences will be found. Bug manifests with integration build I2005-0202. public class Test { public void foo() { Cell c= new Cell("", ""); // calls Cell.Cell(String...) } } class Cell { public Cell(String... args) { } }