Community
Participate
Working Groups
Consider the following QVTo transformation: [code] modeltype ecore uses "http://www.eclipse.org/emf/2002/Ecore"; transformation test(in in1: ecore); main() { test(); } helper test() { return; log("Unreachable statement."); } [/code] The 'log' statement is unreachable. It would be nice if a warning could be produced for it. Note that in Java, unreachable statements are errors. I propose to consider them warnings instead. Considering them errors is irritating for generated code, temporarily commented out stuff, etc.
(In reply to Dennis Hendriks from comment #0) > Considering them errors is irritating for generated > code, temporarily commented out stuff, etc. Treating previously valid code as erroneous is a backward compatibility problem too. I recall another recent Bugzilla about errors and warnings too. Perhaps the time has come for a JDT-like error/warning/severity configurable preference per diagnostic so that users can select whether they like new functionality.
(In reply to Ed Willink from comment #1) > Treating previously valid code as erroneous is a backward compatibility problem too. That's a very good point as well. > I recall another recent Bugzilla about errors and warnings too. Do you mean bugzilla 472482? I recently reported that, and it is about getting rid of warnings for blackbox libraries that are not resolveable in the workspace. Some people might want to see them, some don't. > Perhaps the time has come for a JDT-like error/warning/severity configurable preference per diagnostic so that users can select whether they like new functionality. I think that's a good solution. In fact, I suggested that in bugzilla 472482 as well.
(In reply to Ed Willink from comment #1) > I recall another recent Bugzilla about errors and warnings too. Are you referring to the discussions on control flow analysis? See below. (In reply to Sergey Boyko from bug 414347, comment 3) > For the complex case (control flow analizer) I would create a separate Bug > that will cover all related bugs (bug 414347, bug 413587, bug 255098). +1
