Summary: | IllegalArgumentException in SimpleName.setIdentifier(SimpleName.java:136) in M5 | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Brian Sullivan <bsulliv> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F2 | ||
Hardware: | PC | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Brian Sullivan
2002-05-22 21:14:28 EDT
I just upgraded to F1 to see if that would fix it. I just verified that it appears to have been solved by F1. I would note that it probably should have given the illegal value in the IllegalArgumentException message rather than just using the empty constructor. Olivier - Can you pls double check the assertion message ? The setIdentifier(...) method throws IllegalArgumentException in case the parameter cannot be considered as an valid Java identifier. It uses the empty constructor. Most of the runtime exceptions thrown by AST/DOM have no message. Adding a message would make it *slightly* easier to debug internal errors like this. However, changing the 1000+ occurrences is not a priority. I would suggest to close this PR according to the fact that the initial problem is fixed in F1 and open a new one for the usage of the IllegalArgumentException constructor with a message. Closed. Closed again. |