ruby 1.8.6 (I know, I know!). Parslet 1.2.0. OS is linux RHEL5: Red
Hat Enterprise Linux Server release 5.5 (Tikanga).
It seems plausible that the problem does not occur in 1.9 but does in
1.8. It seems possible but less likely that it appears in 1.8.6 but not
1.8.7, but I don't have time to test it on my 1.8.7 machine at the
moment sorry. (I don't do any 1.9 yet).
It seems unlikely the OS would be relevant, yes?
[But in more positive news, I can't resist saying again I'm having so
much fun and effectiveness with Parslet, it is so well done -- although
like I said I'm not using the Transform stuff, I'm using my own
different approach, but that's just a testament to the greatness of
Parslet, that it doesn't lock you into just one way of doing things,
it's flexible.]
Jonathan
On 3/17/2011 3:12 AM, Kaspar Schiess wrote:
> Hei Jonathan,
>
> I've just created a small stub around the grammar you provided and ran
> it with Ruby 1.9.2, parslet 1.2 on the input you provided and got what
> looks like valid output to me (no exception):
>
> [{:and_list=>[{:token=>"one"@1}, {:token=>"two"@5}, {:token=>"three"@9},
> {:token=>"four"@21}, {:token=>"five"@26}, {:token=>"six"@31}]}]
>
> Here's my setup:
>
> https://gist.github.com/873949
>
> Can you try to be more specific? OS, Ruby and parslet version?
>
> Thanks for your help on tracking this down!
> kaspar
>
