Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 29343

Summary: [M4] Scribbling on missing return statement needs to go on a diet
Product: [Eclipse Project] JDT Reporter: Bob Foster <bob>
Component: CoreAssignee: Philipe Mulet <philippe_mulet>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 2.1   
Target Milestone: 2.1 M5   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Bob Foster CLA 2003-01-12 05:17:30 EST 
This has gotten completely out of hand in M4. A missing return statement can 
result in error highlighting of every line of code in a method, often 
rendering it unreadable. This forces a style of programming where dummy return 
statements must be typed in just so the user can read the code. (When combined 
with the pernicious braces gobble next statement bug, one can spend more time 
working around the assistance than actually writing code.)

Previous releases, too, have error highlighted the wrong code, though not so 
much of it. Lines preceding the missing return are not in error, nor are they  
where this error is detected. Please fix this by doing what you do when there 
are duplicate return statements: flag only the closing right brace.
Comment 1 Philipe Mulet CLA 2003-01-13 04:23:33 EST 

*** This bug has been marked as a duplicate of 27298 ***