Question 1

How to serialize a Common Lisp object to JSON with jzon?

Accepted Answer

Use `jzon:stringify` with the object; for custom serialization, specialize generic functions like `jzon:coerced-fields` or `jzon:write-value` on your class. The README provides examples for `standard-object` and structure objects.

Question 2

jzon vs jsown: which is better for parsing speed?

Accepted Answer

jsown is faster for raw parsing speed, but jzon prioritizes safety and correctness, passing full JSONTestSuite. Choose jsown if speed is critical and JSON is trusted; jzon for secure, RFC-compliant handling.

Question 3

How to handle large JSON files with jzon's streaming API?

Accepted Answer

Use `jzon:with-parser` for incremental parsing with `jzon:parse-next`, or `jzon:with-writer` for streaming output. This avoids loading entire files into memory, as shown in the streaming examples.

Question 4

Can jzon parse JSON with comments or trailing commas?

Accepted Answer

Yes, via keyword arguments: set `:allow-comments t` for // and /* */ comments, and `:allow-trailing-comma t` for trailing commas in arrays/objects. These are disabled by default for RFC compliance.

Question 5

How to customize key names when serializing symbols with jzon?

Accepted Answer

Symbol keys are downcased by default unless mixed-case. Use `:coerce-key` function in `jzon:stringify` or specialize `jzon:write-value` for full control, as detailed in the Custom Serialization section.

Question 6

Is jzon safe for parsing untrusted JSON data?

Accepted Answer

Yes, jzon is designed for safety with limits on nesting, string length, and type-safe APIs to prevent crashes. It avoids infinite interning of strings and uses iterative parsing to prevent stack exhaustion.

jzon

What is jzon?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions