From: Eric Raymond <esr@thyrsus.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Martin Langhoff <martin.langhoff@gmail.com>, git@vger.kernel.org
Subject: Re: More git status --porcelain lossage
Date: Sat, 10 Apr 2010 19:06:10 -0400 [thread overview]
Message-ID: <20100410230610.GB4623@thyrsus.com> (raw)
In-Reply-To: <4BC0FB94.6050409@gnu.org>
Paolo Bonzini <bonzini@gnu.org>:
> >One issue is that there's no stream-parser JSON implementations that
> >I'm aware of.
>
> Here is one. It's ugly as hell, you're warned. The only missing
> piece is making the stack state resizable.
I wrote one in C for the GPSD project that has two interesting
properties:
(1) No use of malloc(),
(2) Unpacks to *fixed-extent* data structures.
It has one language restriction: Array subelements all have to be the same type.
It's not a stream parser, so there will be compile-time limits on the
volume of data it can handle. This isn't a big deal in the GPSD
context, where the objects are relatively short (< 1K) datagrams.
It's very well tested and, I think, pretty bulletproof. I've been thinking
of spinning it out as a reusable project.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2010-04-10 23:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 19:06 More git status --porcelain lossage Eric Raymond
2010-04-09 19:09 ` Eric Raymond
2010-04-09 19:22 ` Jakub Narebski
2010-04-09 19:50 ` Eric Raymond
2010-04-10 4:12 ` Jeff King
2010-04-10 4:14 ` Jeff King
2010-04-10 18:48 ` Simon
2010-04-10 19:01 ` Jakub Narebski
2010-04-10 19:41 ` Eric Raymond
2010-04-10 20:31 ` Martin Langhoff
2010-04-10 22:28 ` Paolo Bonzini
2010-04-10 23:06 ` Eric Raymond [this message]
2010-04-11 11:04 ` David Aguilar
2010-04-10 21:21 ` Jakub Narebski
2010-04-10 22:57 ` Eric Raymond
2010-04-10 19:30 ` Eric Raymond
2010-04-10 19:39 ` Ævar Arnfjörð Bjarmason
2010-04-10 21:24 ` Simon
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=20100410230610.GB4623@thyrsus.com \
--to=esr@thyrsus.com \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.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).