[TIMOB-13191] CodeProcessor: Ambiguous blocks do not handle returns properly
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Critical |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2013-03-25T23:17:20.000+0000 |
| Affected Version/s | Release 3.0.0 |
| Fix Version/s | Release 3.1.0, 2013 Sprint 07 JS, 2013 Sprint 07 |
| Components | Code Processor |
| Labels | qe-devCheck |
| Reporter | Bryan Hughes |
| Assignee | Praveen Innamuri |
| Created | 2013-03-25T18:04:21.000+0000 |
| Updated | 2017-03-09T00:38:43.000+0000 |
Description
Statements that alter the flow of execution outside of am ambiguous block are not handled correctly. There are two ways to do this: returns and throws. Throws are very complex, and I don't know how to handle those yet, but returns are fairly easy (and more common)
Closing ticket as fixed.