[ALOY-195] Drastically improve debugging
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-09-14T09:58:01.000+0000 |
| Affected Version/s | 2012 Sprint 18 |
| Fix Version/s | 2012 Sprint 19, Release 3.0.0 |
| Components | Runtime, XML |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-08-20T11:22:38.000+0000 |
| Updated | 2018-03-07T22:25:48.000+0000 |
Description
We need to improve both the compile time and run time debugging capabilities of Alloy. We need compile breaks to give extremely informative messages, down to file and line if possible. We also need to pursue better runtime debugging, despite the ugliness of some of the generated code. This is an on going task. We can chip away at it 1 day at a time and add to the sprint when time allows.
No comments