Re: [PATCH] Accept plists when serializing and parsing JSON

["João Távora" <joaotavora@gmail.com>]

Yuri Khan <yurivkhan@gmail.com> writes:

> On Wed, May 30, 2018 at 5:31 AM João Távora <joaotavora@gmail.com> wrote:
>
>> Well, it's not really "global state" in the sense I believe you're
>> talking about, because no part of the library is maintaining any state in
>> global variables -- it's read-only from json.c.

> after ironing out all [the other?] bugs related to shared state

Which ones? Those seem to be precisely the ones I meant to say are
excluded because the var is read-only.

> * ‘foo’ wants plists while ‘bar’ wants alists.

If "want" is the same thing as "must have", then bar should be setting
the var from the beginning, end of story. It should only not set the var
if it doesn't care.

There are many variables like this in emacs. Eli recently reminded me in
a closely related thread I have to bind coding-system-for-write around
process-send-string, for example.

Obviously, the pitfall is overlooking to bind them when you have
to. Presumably this is outweighed by the convenience of not passing a
trillion args to a function call and, more importantly, to every caller
of a function, like in the commit that removes the var, which is quite a
bit more complex (which is why I started with the other alternative).

Anyway, this point could be irrelevant if we remove the variable and
argument completely, auto-detecting plists. Can't decide if that could
be a worse idea, though.

João