#1726 closed task (fixed)
Add support for multiple error sources
| Reported by: | perost | Owned by: | perost |
|---|---|---|---|
| Priority: | low | Milestone: | 1.9.4 |
| Component: | Frontend | Version: | |
| Keywords: | Cc: | perost |
Description
Sometimes we want to show both where an error occured and where the cause for that error is. At the moment we use the ERROR_FROM_HERE message to print an error message that tells the user which line caused the error. But it would be better if it was possible to give e.g. addSourceMessage a list of Absyn.Info and allow it to handle this automatically.
Change History (4)
comment:1 Changed 12 years ago by sjoelund.se
- Cc changed from perost, to perost
- Component set to Frontend
- Milestone set to Future
comment:2 Changed 12 years ago by perost
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 9 years ago by dietmarw
- Milestone changed from Future to pre1.9.4
It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.
comment:4 Changed 7 years ago by sjoelund.se
- Milestone changed from pre1.9.4 to 1.9.4
Removing the pre1.9.4 milestone in favor of 1.9.4.
Note: See
TracTickets for help on using
tickets.
Fixed in r15455 with the introduction of Error.addMultiSourceMessage.