Closed
Bug 415747
Opened 17 years ago
Closed 17 years ago
coordinates for syntax errors incorrect/incomplete
Categories
(Tamarin Graveyard :: Self-hosting compiler (ESC), defect)
Tamarin Graveyard
Self-hosting compiler (ESC)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markh, Assigned: markh)
Details
Attachments
(1 file)
|
4.03 KB,
patch
|
Details | Diff | Splinter Review |
Util::internalError doesn't pass on its |file| or |line| params (and actually passes |msg| as |file|). column coordinates aren't passed at all.
I'm attaching a patch that fixes most of this. However, please note:
* I think an off-by-1 error remains in the column coord, but replacing all assignments of colCoord to 0 with 1 didn't seem to fix it, and I don't care enough to dig further (nor to argue if column zero exists :)
* We assign a 'column' attribute to the SyntaxError, but I'm not sure if there is a precedent for a different name (ie, does ASC set such an attribute?)
* cogen.es still passes 0 as the column number - I can't see where that is tracked. I'm not sure if this is a problem in practice.
| Assignee | ||
Comment 1•17 years ago
|
||
Comment 2•17 years ago
|
||
I'm about to land a major rewrite of the entire front end, so this patch has limited applicability. Line number tracking has changed, and I'm doing away with column coordinates completely.
I'd prefer if we discard the present patch so that it doesn't create needless merge trouble for me. But we can keep the bug open and I'll mine the patch for insight when I get ready to ship the rewrite.
The rewrite should be ready thursday/friday of this week but may come as late as next week (meetings, travel).
Comment 3•17 years ago
|
||
A similar but not equivalent fix has been posted as part of the cleanup in bug 416454.
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 5•17 years ago
|
||
Comment on attachment 301465 [details] [diff] [review]
fix coords for syntax errors
Superseded by other fix.
Attachment #301465 -
Flags: review?(lhansen)
You need to log in
before you can comment on or make changes to this bug.
Description
•