From: git@jeffhostetler.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net, l.s.r@web.de, wink@saville.com,
ramsay@ramsayjones.plus.com,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v4] routines to generate JSON data
Date: Mon, 26 Mar 2018 14:31:35 +0000 [thread overview]
Message-ID: <20180326143136.47116-1-git@jeffhostetler.com> (raw)
From: Jeff Hostetler <jeffhost@microsoft.com>
This is version 4 of my JSON data format routines.
This version adds a "pretty" formatted output. I consider this to be
mainly for debugging, but worth keeping available in release builds.
I simplified the stack-level tracing as suggested by René Scharfe and
hinted at by Peff.
I converted the _double() routines to take an integer precision rather
than a format specification and build a known-to-be-good format string
to minimize the __attribute__(...) issues raised by René Scharfe.
It fixes the PRIuMAX and "void inline" compiler warnings on OSX that
were reported by Wink Saville and Ramsay Jones. And resolved the "sparse"
warnings repoted by Ramsay Jones.
And I updated the commit message and header file documnetation to address
the JSON-like (Unicode limitations) mentioned by Jonathan Nieder.
Jeff Hostetler (1):
json_writer: new routines to create data in JSON format
Makefile | 2 +
json-writer.c | 395 +++++++++++++++++++++++++++++
json-writer.h | 92 +++++++
t/helper/test-json-writer.c | 590 ++++++++++++++++++++++++++++++++++++++++++++
t/t0019-json-writer.sh | 253 +++++++++++++++++++
5 files changed, 1332 insertions(+)
create mode 100644 json-writer.c
create mode 100644 json-writer.h
create mode 100644 t/helper/test-json-writer.c
create mode 100755 t/t0019-json-writer.sh
--
2.9.3
next reply other threads:[~2018-03-26 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 14:31 git [this message]
2018-03-26 14:31 ` [PATCH v4] json_writer: new routines to create data in JSON format git
2018-03-27 3:18 ` Ramsay Jones
2018-03-27 10:28 ` Jeff Hostetler
2018-03-27 15:45 ` Ramsay Jones
2018-03-27 17:14 ` Jeff Hostetler
2018-03-27 17:43 ` Wink Saville
2018-03-27 18:00 ` Randall S. Becker
2018-03-28 5:22 ` Junio C Hamano
2018-03-27 18:05 ` Ramsay Jones
2018-03-28 1:22 ` Junio C Hamano
2018-06-02 4:41 ` Duy Nguyen
2018-06-02 5:13 ` Jeff King
2018-06-04 9:41 ` Jeff Hostetler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180326143136.47116-1-git@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
--cc=wink@saville.com \
/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 NNTP newsgroup(s).