Opened 16 years ago
Closed 16 years ago
#253 closed defect (fixed)
Improve syntax exception reporting
| Reported by: | Stephen Siegel | Owned by: | bperry |
|---|---|---|---|
| Priority: | major | Milestone: | 1.1 |
| Component: | front | Version: | 1.1 |
| Keywords: | syntax exception error reporting | Cc: |
Description
There is a nice SyntaxException class, but it is not used in many many places in the front end. Instead, various runtime exceptions are thrown and the error reports are often cryptic.
Someone needs to go through the whole front end and check that all syntax exceptions are dealt with in a common way : throwing a SyntaxException with a non-null Source info and good, clear message. The exceptions are caught up in the verify module and reported correctly.
Change History (4)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Milestone: | Release 1.0 → 1.1 |
|---|---|
| Version: | 1.0 → 1.1 |
comment:3 by , 16 years ago
| Status: | new → accepted |
|---|
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
Runtime exceptions and System.exit()'s have been changed to SyntaxExceptions.
Note:
See TracTickets
for help on using tickets.

FYI: I made front-end expressions sourceable, so now they can be passed to a SyntaxException.