Ripper and RRB

[Jonathan Maasland]

The last two to three weeks I've been poking in and around Ripper and I
finally managed to get a new version to compile and parse the entire
Ruby-source-tree.

Laurent, Curt: When I'm finished with the new Ripper sources shouldn't
we keep a copy of it in our CVS-repo??

An interesting issue I ran into is that RRB uses a modified version of
Ripper.
It is possible to use the two versions simultaneously because RRB's
Ripper is defined under the RRB module and is also named rrb_ripper.so
but when comparing our SourceParser structs with RRB's I believe RRB is
far more complete.
I'd really hope to be able integrate RRB's parser in FreeRIDE. It is
pretty complex to figure out because I've got to find the modifications
they made to the old Ripper and port them to the new Ripper.

Any ideas/suggestions/comments are welcome.

(ps. I've also been looking at ruby-debug and I'll look into the
possibility of integrating it once I'm finished with the Ripper and RRB
code (prolly gonna take quite a while))

With friendly greetings,
Jonathan
_______________________________________________
Freeride-devel mailing list
Freeride-devel@...
http://rubyforge.org/mailman/listinfo/freeride-devel

[Laurent Julliard]

Jonathan,

Thanks for the update.
I think we should keep the new ripper source in our CVS repo and build
the .so as part of our build process. At first we only committed the
library hoping that the ripper developers would keep up with the
modifications, etc.. but it didn't happen.

If I remember well RRB has a number of additional features compared to
ripper such as returning the offset of token in the original source
file. Keeping RRB is definitely what we should be if you believe this is
achievable of course.

I looked at ruby-debug very quickly the other day as a possible
alternative to the current debugger module which is really very flaky
especially on Windows. I found it to be an interesting approach although
a number of key features seem to be missing.

Keep up doing th good work Jonathan! On my side I have as a plan to use
each and every plugin to make sure that there are no other bugs left
after the migration from FOX 1.2 to FOX 1.4

Laurent

Laurent

Jonathan Maasland wrote:

> The last two to three weeks I've been poking in and around Ripper and I
> finally managed to get a new version to compile and parse the entire
> Ruby-source-tree.
>
> Laurent, Curt: When I'm finished with the new Ripper sources shouldn't
> we keep a copy of it in our CVS-repo??
>
> An interesting issue I ran into is that RRB uses a modified version of
> Ripper.
> It is possible to use the two versions simultaneously because RRB's
> Ripper is defined under the RRB module and is also named rrb_ripper.so
> but when comparing our SourceParser structs with RRB's I believe RRB is
> far more complete.
> I'd really hope to be able integrate RRB's parser in FreeRIDE. It is
> pretty complex to figure out because I've got to find the modifications
> they made to the old Ripper and port them to the new Ripper.
>
> Any ideas/suggestions/comments are welcome.
>
> (ps. I've also been looking at ruby-debug and I'll look into the
> possibility of integrating it once I'm finished with the Ripper and RRB
> code (prolly gonna take quite a while))
>
> With friendly greetings,
> Jonathan
> _______________________________________________
> Freeride-devel mailing list
> Freeride-devel@...
> http://rubyforge.org/mailman/listinfo/freeride-devel
>

_______________________________________________
Freeride-devel mailing list
Freeride-devel@...
http://rubyforge.org/mailman/listinfo/freeride-devel