From: Eric Mahurin <eric.mahurin@...>
Date: 2008-02-08T00:38:41+09:00
Subject: Re: Parsing JSON (#155)

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

On Feb 7, 2008 6:30 AM, tho_mica_l <micathom@gmail.com> wrote:

> Hi,
>
> >      - 191529 2 1  445 Thomas Link (RE lexer, ruby eval)
> > 359665 279539 3 0  405 Thomas & Paolo (RE + eval)
>
> May I ask which test are missing here, since it passes all my test.
>

I'm running all tests from this thread.  Here are the ones that the above
solutions failed:

   assert_raise(RuntimeError) { @parser.parse(%Q{"a" "b"}) }
   assert_equal( "a", @parser.parse(%Q{"\\u#{"%04X" % 97}"}) )  # 97 was ?a,
1.9 compat.
   assert_equal('#{p 123}', @parser.parse(%q{"\\u0023{p 123}"}))

Maybe the versions of these I have are old.


>
> > 2079190     - 0 0  653 Eric Mahurin (Grammar, unreleased, ruby2cext)
>
> This made me quite curious. Unfortunately it seems ruby2cext doesn't
> support ruby19 yet. Anyway, will this coming-up version of grammar be
> a drop-in replacement/update for grammar 0.5, i.e. is it safe to use
> grammar 0.5 now?


I'll have a compatibility layer that will use the new stuff.  You'll still
get all of the performance benefits, but this will ease any transition.
Most of the API changes will be minor.  It will be a cleaner API.

------=_Part_22081_11494273.1202398725961--