newlispfanclub.alh.net

Posted: **Tue Feb 05, 2008 4:25 am**

Seems like a bug in newlisp:

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

> {

string token too long : "\r\n\000\0046\0047\0048\0049\004:\004;\004<004>\0
04?\004@\004A\004B\004C\004D\004E\004F\004G\004"

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

Posted: **Tue Feb 05, 2008 6:54 am**

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

newlispfanclub.alh.net

Parsing bug?

Parsing bug?