#1726 closed task (fixed)
Add support for multiple error sources
Reported by: | Per Östlund | Owned by: | Per Östlund |
---|---|---|---|
Priority: | low | Milestone: | 1.9.4 |
Component: | Frontend | Version: | |
Keywords: | Cc: | Per Östlund |
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 by , 12 years ago
Cc: | perost, → perost |
---|---|
Component: | → Frontend |
Milestone: | → Future |
comment:2 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 9 years ago
Milestone: | Future → 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 by , 7 years ago
Milestone: | pre1.9.4 → 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.