On 27 Feb 2014, at 13:56, Jan Vrany <[email protected]> wrote: > On 24/02/14 19:06, Marcus Denker wrote: > >> >> Pharo uses (right now) RBParser as the main Parser… in Pharo4 we will remove >> the old Parser (subclass of Scanner ;-), >> on the TODO is to check if PetitParser can be used instead (but there are >> many open questions related to e.g. error handling, >> speed…) > > This is interesting for me. I would not go for petitparser personally. > My experience, speaking of performance and error reporting, not so > great.
+1 I would not mind to have two. One for experimental interactive...and the other for production and heavy dutie. Now to me we have so many more important aspects to improve that I would not really build a case for that. > > I have one question: If you replace RBParser with green-field implementation, > how would you deal with the rest of RB stuff? > Refactorings, lint etc, which are all based of RBParser API? > > > Best, Jan >
