Regarding completeness, it is not great. It was implement with an emphasiz on the indentation/prefix-related part (the hard one, I hope) so quoted blocks and and lists are almost complete (with arbitrary nesting). I did not need the other stuff, so there is a basic support for headers, paragraphs and code blocks. I followed the commonmark spec ( http://spec.commonmark.org/0.17/).
If there is an interest to use PetitParser/CommonMark in Pharo, I can spend some time on it. I guess, I would be able to parse majority of the examples (I am not sure about all the corner cases). Cheers, Jan On 14 April 2015 at 14:24, Peter Uhnák <[email protected]> wrote: > On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < > [email protected]> wrote: > >> >> Le 14 avr. 2015 à 11:43, Esteban Lorenzano a écrit : >> >> > how complete it is? >> > we would really like to think on: >> > >> > 1) include petitparser in Pharo >> > 2) allow the writing of class docs in MD format :) >> >> I would prefer pillar for class / packages comments >> > > I was quite surprised there are any MD defendants considering the pillar > push. But since diversity is (often) a good think maybe having something > like gt-inspector there would be cool where you can add this in whatever > format you want. (And maybe one day someone will write pillar to > morphic/whatever converter and it would be even cooler.) > > Peter > > >
