Lexical violation message typo
Bug #305857 reported by
Derick Eddington
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ikarus Scheme |
Fix Committed
|
Low
|
Abdulaziz Ghuloum | ||
Bug Description
Ikarus Scheme version 0.0.3+ (revision 1700, build 2008-12-06)
Copyright (c) 2006-2008 Abdulaziz Ghuloum
> #Toops
Unhandled exception
Condition components:
1. &lexical
2. &message: "invalid syntax near #o"
3. &lexical-position:
file-name: *stdin*
character: 3
>
It's supposed to be "... near #\o", right?
Related branches
| Changed in ikarus: | |
| importance: | Undecided → Low |
Revision history for this message
| Abdulaziz Ghuloum (aghuloum) wrote | #1 |
| Changed in ikarus: | |
| assignee: | nobody → aghuloum |
| status: | New → Fix Committed |
| Changed in ikarus: | |
| milestone: | none → 0.0.4 |
To post a comment you must log in.
Fixed in 1706. It now says "... near #To".