Error message is not correct for ~@R with 0.
Bug #1967138 reported by
SATO shinichi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SBCL |
New
|
Undecided
|
Unassigned | ||
Bug Description
This is not a bug, just a wish list.
The minimum example is below.
(format t "~@R" 0)
debugger invoked on a SIMPLE-ERROR in thread
#<THREAD ...>:
Number too large to print in Roman numerals: 0
Revision history for this message
| Douglas Katzman (dougk) wrote | #1 |
To post a comment you must log in.
Funny- same error message from ECL, ABCL, CMUCL. Reasonable message from CCL and CLISP.
I suppose we should make it "0 is not representable as a Roman numeral"
Also we can extend the range now that Unicode is a thing. A Google search finds Roman numeral tables up to 1 million using the vinculum character (https:/