Hi, > Am 11.08.2017 um 21:10 schrieb Esteban Lorenzano <esteba...@gmail.com>: > > hi, > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferli...@gmail.com >> <mailto:cyril.ferli...@gmail.com>> wrote: >> >> Another step would be to get a minimal parser not relying on >> PetitParser. > > Let’s think differently: why not to include a tiny PetitParser? > Then we can think on: > > - pillar sintax (better than just a restricted version) > - simplify other “small parsers” that are already on the image. > - we provide a tool to o cool stuff (instead relying as always in regexp, > etc.) >
+1 I like that. I always feel bad if I use regex in pharo because I think I can do better. But then installing petit parser just to do some parsing sounds heavy weight. And parsing is such central functionality that it would be good to have a small parser near the core. For pillar I would like to see that class comments are a layer on top of the image core. It is metadata that can be optional and pillar could be a dependency to that layer. This would make it possible to strip out on deployment, too. Because I don't need class comments on my server :) Norbert
