Thanks, that's exactly what I was wondering. That would be a valuable clarification in the book. Is there an issue tracker? -------- Original message -------- From: "Damien Cassou [via Smalltalk]" <ml-node+s1294792n4719808h36@n4.nabble.com> Date: 11/07/2013 7:38 AM (GMT-05:00) To: "Sean P. DeNigris" <sean@clipperadams.com> Subject: Re: Deep Into Pharo: PPExpressionParser On Wed, Nov 6, 2013 at 12:41 PM, Sean P. DeNigris <[hidden email]> wrote:
Thanks! I'm clear on how to use them, just not on why to choose one over the other..
I would say you can instantiate a PPExpressionParser if you want to do a small parser for small task. Now, if you have a grammar that's composed of many parsers, I would subclass PPCompositeParser. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill If you reply to this email, your message will be added to the discussion below: http://forum.world.st/Deep-Into-Pharo-PPExpressionParser-tp4719454p4719808.h... To unsubscribe from Deep Into Pharo: PPExpressionParser, click here. NAML ----- Cheers, Sean -- View this message in context: http://forum.world.st/Deep-Into-Pharo-PPExpressionParser-tp4719454p4719909.h... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.