Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/... On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
and btw, this kind of threads belongs to pharo-dev, not to pharo-users :)
Esteban
On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 12 Aug 2017, at 12:46, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I would very much like this path. What would constitute tiny?
no idea, we need to think on it :) but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.).
Esteban
Cheers, Doru
On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm@gmail.com>
wrote:
hi,
On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot@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.)
cheers, Esteban
-- www.tudorgirba.com www.feenk.com
"Beauty is where we see it."
-- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13