Hi Tobias,
The named-readtables test you sent me, does show an obvious bug in ABCL, but not the one you're trying to point me at: when loading your files on Windows, I'm getting an Index out of bounds error: the dispatch tables think our characters range from 0 - 255 in value whereas in practice that number is much higher.
I'm working on a fix right now (setting CHAR_MAX to a higher value) but I don't feel too comfortable with it: it'll make us consume much more memory on a number of things. However, what's a K of memory worth these days... ?
Bye,
Erik.
Ok. Fix for the character-size issue committed.
With that fix I'm now able to evaluate the form you sent me:
(named-readtables:make-readtable :new-readtable) --> #<READTABLE {...} >
I hope this fixes it for you too.
Bye,
Erik.
On Sun, Sep 20, 2009 at 10:16 PM, Erik Huelsmann ehuels@gmail.com wrote:
Hi Tobias,
The named-readtables test you sent me, does show an obvious bug in ABCL, but not the one you're trying to point me at: when loading your files on Windows, I'm getting an Index out of bounds error: the dispatch tables think our characters range from 0 - 255 in value whereas in practice that number is much higher.
I'm working on a fix right now (setting CHAR_MAX to a higher value) but I don't feel too comfortable with it: it'll make us consume much more memory on a number of things. However, what's a K of memory worth these days... ?
Bye,
Erik.
Erik Huelsmann writes:
Hi Tobias,
The named-readtables test you sent me, does show an obvious bug in ABCL, but not the one you're trying to point me at: when loading your files on Windows, I'm getting an Index out of bounds error: the dispatch tables think our characters range from 0 - 255 in value whereas in practice that number is much higher.
I'm working on a fix right now (setting CHAR_MAX to a higher value) but I don't feel too comfortable with it: it'll make us consume much more memory on a number of things. However, what's a K of memory worth these days... ?
I haven't read through ABCL's reader sources, but the dispatch tables (as well as unicode macro characters) should be maintained lazily, probably in some sort of associative map.
-T.
armedbear-devel@common-lisp.net