------art_10250_30547316.1201882911726
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Feb 1, 2008 10:12 AM, James Gray <james / grayproductions.net> wrote:

> On Feb 1, 2008, at 10:09 AM, Eric Mahurin wrote:
>
> > On Feb 1, 2008 7:55 AM, Ruby Quiz <james / grayproductions.net> wrote:
> >
> >> In honor of that, this week's Ruby Quiz is to write a parser for
> >> JSON.
> >>
> >> JSON turns out to turns out to be a great little example for writing
> >> parsers for
> >> two reasons.  First, it's pretty easy stuff.  You can hand-roll a
> >> JSON
> >> parser in
> >> under 100 lines of Ruby.  The second advantage is that the data
> >> format is
> >> wonderfully documented:
> >>
> >>       http://json.org/
> >>
> >
> > I definitely want to find time to do this one.  What would be nice
> > to have
> > is performance benchmark to compare parsers.  Maybe just have a
> > little ruby
> > script that generates a stream of repeatable random (but valid) JSON.
>
> Neat idea.
>
> Just FYI though, I'm probably going to focus more on the parsing in
> the summary that the speed.
>
> James Edward Gray II


OK.  Once I figure out exactly what JSON is, I'll probably make a random
JSON generator.

Hopefully this will make me do another release of my parser package, which
is long overdue :).  At least check-in my local code into CVS.

------art_10250_30547316.1201882911726--