Parsing bug?

[Cyril]

Seems like a bug in newlisp:

Code Select Expand

newLISP v.9.3.0 on Win32, execute 'newlisp -h' for more info.

> {

string token too long : "rn0004604704804904:04;04<004>
04?04@04A04B04C04D04E04F04G04"


Seems like parsing of {)-balanced string doesn't stop on rn or even on null byte. parse function is also affected.

[Lutz]

No worries. This is only an issue with the error reporting 40 bytes of un-ininialized token buffer and will be fixed in a future version. The parser code itself is safely stopping at the first 0 byte it finds and will never overrun the token buffer.



Lutz