Summary: | Wrong "Empty control-flow statement" error | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | CLOSED INVALID | QA Contact: | |
Severity: | major | ||
Priority: | P3 | CC: | dirk_baeumer |
Version: | 3.0 | Keywords: | needinfo |
Target Milestone: | 3.1 RC2 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Dani Megert
2004-04-29 03:35:28 EDT
This option just got added, Martin is adding preference for it. I don't get why it would default to an ERROR. It should default to IGNORE, thus you shouldn't see it. I changed the code so I'm not 100% sure but I think the reconcile which reports temporary problems work correctly but the builder generated an error marker. Actually, I got confused. The severity is controlled by the preference "unnecessary semicolon" which is going to be renamed into "empty statement" or something like that. The question now is: did you make this problem be an error ? yes Ok closing, once the option is renamed it will be fine. I still think this is a bug: before I could have while (time < 50) ; and statement;; where I only was informed about latter code and the first was treated as valid code. These two are now folded together i.e. I get both reported with same severity. I would either like to have separate options or treat the first one as valid as it has been before. More options is always possible, but we discussed with Dirk and Martin, and they agreed we should fold these options together. Hint: if you want to address the warning for the control-flow statement, simply replace the semicolon with {/*empty*/}. Will keep this request as reminder if more people complain. Dirk, please revisit your decision. We have really lost functionality here and the code gets worse and not better because people simply decrease or disable this option. Erich agreed as well. If you think this bug should be reconsidered for 3.1, then please reopen asap. Otherwise, just close it, thanks. I still think it should be reconsidered but I leave it up to Dirk. He's back next week. Close as no more people complain about current behavior As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you. |