Only partially -- I managed to get the whole parser working, BAR the
comments... I had tried to embed the comment 'detection' into the
"whitespace" rule ("W"), but I never managed to get it to work, so I
yanked the comment bit for now..I think there's probably a need in ragel to specify a "skip" rule flag, to prevent the parser getting gigantic with "instances" of these empty rules... I tried to do an fcall/fret but didn't get that to work either... Right now the parser is about 50kb expanded, and thats as low as I managed it to get, I think that given the relative complexity of it, it's probably OK... If you want to have a quick review and/or submit patches, I would be very grateful ! Michael On Wed, Sep 29, 2010 at 7:21 PM, Adrian Thurston <[email protected]> wrote: > Thanks! > > I'm very sorry I never responded to your messages. Did you get all the > issues worked out? > > -Adrian > > On 10-09-29 11:19 AM, M P wrote: >> >> I open-sourced a ragel-based parser for an extended version of JSON (I >> had posted a problematic version some weeks ago) >> >> >> http://bliterness.blogspot.com/2010/09/new-libejson-json-parser-on-steroids.html >> >> Michael >> >> _______________________________________________ >> ragel-users mailing list >> [email protected] >> http://www.complang.org/mailman/listinfo/ragel-users >> > > _______________________________________________ > ragel-users mailing list > [email protected] > http://www.complang.org/mailman/listinfo/ragel-users > _______________________________________________ ragel-users mailing list [email protected] http://www.complang.org/mailman/listinfo/ragel-users
