Hi Frank, Likely this has nothing to do with PetitParser.
>From my understanding: In Clamato the parser was running at the language level (Smalltalk). JTalk introduced a dead-slow method lookup and as a consequence they optimize the parser by moving it to the implementation level (a JavaScript primitive). Lukas On 14 September 2011 09:30, Frank Shearar <[email protected]> wrote: > Hi Göran, > > Quick question: during your work on Amber, did you find any > particularly slow parts of PetitParser? > > Or, rephrased: while a hand-written parser is pretty much guaranteed > to run faster than PetitParser (or any general parser generator, I > reckon), are there any parts of PetitParser that leap out as being > ripe for optimisation? > > Thanks, > > frank > > -- Lukas Renggli www.lukas-renggli.ch
