jsown

jsown copied to clipboard

Memory Fault Error on SBCL when given bad JSON

1

Hey, Attempting to parse the following incorrect JSON makes SBCL 2.0.8 pause for several seconds, then raise the error "Unhandled memory fault at #x1200000000. [Condition of type SB-SYS:MEMORY-FAULT-ERROR]". ```lisp (jsown:parse...

MistressRemilia

When parsing strings that have form feeds (\f) and new lines (\n) the parse function translate this escape character to the same common lisp value (#\linefeed), so if you compare...

kongotania

Hello, A literal ^M character in a string will cause jsown to misparse numbers. In the code below I wrote ^M as explicitly two characters where you could see it,...

psilord

When invoking `parse` with the keywords to scan, it appears to return keys and values for partial matches, which does not appear to be the intent (at least not from...

garethw14

`to-json*` prints empty string instead of `{}` for empty object

4

`to-json*` prints an empty string instead of `{}` for an empty object: * (jsown:to-json (jsown:empty-object)) "{}" * (jsown:to-json* (jsown:empty-object)) "" This is on Void Linux with SBCL 1.3.17 and jsown-20160208-git.tgz...

aerique

Cannot parse bare numbers

6

``` * (jsown:parse "12345") debugger invoked on a SB-KERNEL:BOUNDING-INDICES-BAD-ERROR in thread #: The bounding indices 0 and 9416 are bad for a sequence of length 5. See also: The ANSI...

jasom