From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: guile-json 3.0.0 released
Date: Sat, 29 Dec 2018 22:27:38 -0800 [thread overview]
Message-ID: <CA+XASoVmEy1Rt7w=pM21JkYL6dYJeGtW0_HjpnUa_eV5pGcvkQ@mail.gmail.com> (raw)
Hi,
I'm pleased to announce guile-json 3.0.0. This is another breaking
change release (hopefully no one had time to update to 2.0.0). Thanks
to everyone for all the comments.
https://github.com/aconchillo/guile-json
* Changes in 3.0.0
- JSON objects are now defined as alists (instead of hash tables) and
JSON arrays are now defined as vectors (instead of lists). Both of
these changes are mainly to use types that have read syntax. This will
simplify things for the user when defining JSON objects which is
probably the most common case.
- Fixed and issue when parsing only JSON numbers.
- Added unit tests.
Happy hacking!
Aleix
next reply other threads:[~2018-12-30 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 6:27 Aleix Conchillo Flaqué [this message]
2019-01-01 5:54 ` guile-json 3.0.0 released Aleix Conchillo Flaqué
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+XASoVmEy1Rt7w=pM21JkYL6dYJeGtW0_HjpnUa_eV5pGcvkQ@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).