+1

PetitMarkdown (at least in the state I left it) had an incomplete and
contorted grammar, translated from another implementation (the one used by
pandoc, I think). I started something to handle indentation, but meh. Jan's
extension of PetitParser is the way to go, and it should make the grammar
way more readable.

On 14 April 2015 at 11:43, Esteban Lorenzano <[email protected]> wrote:

> 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 :)
>
> of course, we are talking about the not-so-near future, but is an idea we
> are thinking about… :P
>
> and in any case, I would like to use a good MD parser for my own stuff :)
>
> Esteban
>
> On 14 Apr 2015, at 10:42, Jan Kurš <[email protected]> wrote:
>
> Hey,
>
> I also created an indentation sensitive extension of PetitParser, I also
> included some examples including Markdown. If you load PetitParser, you get
> the Markdown example as well.
>
> There is a short introduction to the indentation:
>
> http://scg.unibe.ch/research/indentParsing
>
> Cheers Jan
> On Apr 13, 2015 5:24 PM, "H. Hirzel" <[email protected]> wrote:
>
>> Are there any news on this?
>>
>> --Hannes
>>
>> On 12/28/14, Norbert Hartl <[email protected]> wrote:
>> > I found markdown parsers in smalltalkhub and in the configuration
>> browser.
>> >
>> > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/
>> > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/>
>> >
>> > and the one in the configuration browser
>> >
>> > PPMarkdown
>> >
>> > If I understand it correctly both are rooted into work Camillo did. The
>> one
>> > in PharoExtras looks newer to me. So I assume the best would be to copy
>> the
>> > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and
>> remove
>> > the ConfigurationOfPPMarkdown. Right? Or are there any objections?
>> >
>> > Norbert
>>
>>
>


-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Reply via email to