Re: [PATCH] Support custom 'null' and 'false' objects when parsing JSON

[Stefan Monnier]

> the keyword :null, I have to explicitly check for non-`nil'ness *and*
> non-`:null'ness, whereas before only one check was necessary.  Other

IIUC this is a matter of changing things like

    (null x)
to
    (memq x '(nil :null))

right?  On this one example it doesn't look that bad, so I'm wondering
about the real impact it would have on your code.

> -json_to_lisp (json_t *json, enum json_object_type object_type)
> +json_to_lisp (json_t *json,
> +              enum json_object_type object_type,
> +              Lisp_Object null_object,
> +              Lisp_Object false_object)

Wouldn't it make sense to group those 3 parameters into a single object
(presumably a pointer to a stack-allocated struct containing those
3 fields)?


        Stefan