|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
|
|
Still working on ripperHi all,
I just thought I'd let you all know that I'm still working on Ripper and fixing bugs. Still got 7 bugs to fix before I'm done. Currently I'm constructing test-cases which will allow for easy verification of the correct working of Ripper. I was just wondering about how and when I should commit the sources. I've been thinking two different routes and I'd like some feedback before proceeding. The obvious first route is to commit everything as one big addition once I'm finished. The second route is to start committing right now and commit changes once I fix a certain bug. I'm kind of leaning towards the second, but like I said I'd like to receive some feedback before I do actually commit. With a friendly greeting, Jonathan _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripperOn 7/9/07, Jonathan Maasland <nochoice@...> wrote:
Hi all, It doesn't really matter to me, whatever you are more comfortable with. My question would be to Laurent: do you want to wait on this before building & releasing 0.9.7? Curt _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripper
Well I just finished fixing the last of the bugs. Ripper now correctly
parses my Ruby dist-files (1.8.6). I still have to check it against the
all the sources provided by the OneClick Ruby installer and against
InstaRails. I'll do that this afternoon and report back as soon as I
get the results. Just wanted to let you know the good news already.
With kind regards, Jonathan Curt Hibbs wrote: On 7/9/07, Jonathan Maasland <nochoice@...> wrote: _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripper
Well I'm still not done yet. I'm getting some errors parsing the
One-click-installer directory.
I'll keep you posted as I go along. Jonathan Jonathan Maasland wrote: Well I just finished fixing the last of the bugs. Ripper now correctly parses my Ruby dist-files (1.8.6). I still have to check it against the all the sources provided by the OneClick Ruby installer and against InstaRails. I'll do that this afternoon and report back as soon as I get the results. Just wanted to let you know the good news already.-snip- _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripperGuys,
I'm back from a long trip and reconnecting with you. Given that 0.9.7 is not yet out I think we can wait for your new ripper Jonathan. This will be a sifgnificant contribution to 0.9.7 Let me know when your are done with testing and commit. Laurent Jonathan Maasland wrote: > Well I just finished fixing the last of the bugs. Ripper now correctly > parses my Ruby dist-files (1.8.6). I still have to check it against the > all the sources provided by the OneClick Ruby installer and against > InstaRails. I'll do that this afternoon and report back as soon as I get > the results. Just wanted to let you know the good news already. > > With kind regards, > Jonathan > > Curt Hibbs wrote: >> On 7/9/07, *Jonathan Maasland* <nochoice@... >> <mailto:nochoice@...>> wrote: >> >> Hi all, >> >> I just thought I'd let you all know that I'm still working on >> Ripper and >> fixing bugs. Still got 7 bugs to fix before I'm done. >> >> Currently I'm constructing test-cases which will allow for easy >> verification of the correct working of Ripper. >> >> I was just wondering about how and when I should commit the sources. >> I've been thinking two different routes and I'd like some feedback >> before proceeding. >> >> The obvious first route is to commit everything as one big >> addition once >> I'm finished. >> The second route is to start committing right now and commit changes >> once I fix a certain bug. >> >> I'm kind of leaning towards the second, but like I said I'd like to >> receive some feedback before I do actually commit. >> >> >> It doesn't really matter to me, whatever you are more comfortable with. >> >> My question would be to Laurent: do you want to wait on this before >> building & releasing 0.9.7? >> >> Curt >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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 _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripper
Laurent,
Unfortunately I've been too busy last month to work on Ripper and to be honest it's starting to become a bit too diffucult to keep working on it. The complexity of Ripper is really starting to get to me. All the showstopper bugs have been fixed, ie. it doesn't segfault anymore. However certain constructs still can't be parsed. For example "module ::Types" and several others. I've looked at other parsers but there doesn't seem to be one out there that parses the Ruby-sources correctly other than ANTLR. My biggest problem however is that my Windows machine broke down and I'm unable to compile Ripper on Windows. Therefore I'd like to ask someone here on the list to help me out with it. Contact me off-list so I'll be able to provide you with the sources. I'd be really really grateful if someone could help me out with that. With friendly greetings, Jonathan Laurent Julliard wrote: Guys, I'm back from a long trip and reconnecting with you. Given that 0.9.7 is not yet out I think we can wait for your new ripper Jonathan. This will be a sifgnificant contribution to 0.9.7 Let me know when your are done with testing and commit. Laurent Jonathan Maasland wrote: _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
|
|
Re: Still working on ripperJonathan,
Has anyone contacted you and offer help to compile the ripper parser on Windows? If not can sbdy on the mailing list volunteer for this ? We need this library before we release FR 0.9.7 Can you also increment the version number of your ripper and send me a tar.gz of your sources so that I can recompile it on Linux. Thanks Jonathan Maasland wrote: > Laurent, > > Unfortunately I've been too busy last month to work on Ripper and to be > honest it's starting to become a bit too diffucult to keep working on > it. The complexity of Ripper is really starting to get to me. > > All the showstopper bugs have been fixed, ie. it doesn't segfault > anymore. However certain constructs still can't be parsed. > For example "module ::Types" and several others. I've looked at other > parsers but there doesn't seem to be one out there that parses the > Ruby-sources correctly other than ANTLR. > > My biggest problem however is that my Windows machine broke down and I'm > unable to compile Ripper on Windows. Therefore I'd like to ask someone > here on the list to help me out with it. Contact me off-list so I'll be > able to provide you with the sources. I'd be really really grateful if > someone could help me out with that. > > With friendly greetings, > Jonathan > _______________________________________________ Freeride-devel mailing list Freeride-devel@... http://rubyforge.org/mailman/listinfo/freeride-devel |
| Free Forum Powered by Nabble | Forum Help |