[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#55278: json-parse-string
From: |
Richard Stallman |
Subject: |
bug#55278: json-parse-string |
Date: |
Mon, 09 May 2022 19:20:32 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> The two libraries aren't really compatible without reparsing the entire
> parse tree returned by them. For instance, the C library returns:
> (json-parse-string "null")
> => :null
> While json.el says:
> (json-read-from-string "null")
> => nil
No deep difference between them is visible in this example.
What is the a deep difference?
Is there a reason why they _must_ give different output formats
or is that difference just for historical reasons?
Could we make a version of the Lisp code
that produces the same output as jansson?
It would be slower but that is better than not running.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
- bug#55278: json-parse-string, (continued)
- bug#55278: json-parse-string, Daniel Mendler, 2022/05/08
- bug#55278: json-parse-string, Richard Stallman, 2022/05/08
- bug#55278: json-parse-string, Richard Stallman, 2022/05/09
- bug#55278: json-parse-string, Richard Stallman, 2022/05/16
- bug#55278: json-parse-string, Philip Kaludercic, 2022/05/17
- bug#55278: json-parse-string, Richard Stallman, 2022/05/18
- bug#55278: json-parse-string,
Richard Stallman <=
- bug#55278: json-parse-string, Richard Stallman, 2022/05/09