Carsten Brandt

yep, thinking about this. maybe we could use traits to combine different flavors. thats why I want to decide on #8 later.

smarty pants do not have priority for me. Not sure when I get it done.

needs a structural change of how the absy is represented and how rendering/parsing functions access the absy. Needs BC break, so set for 2.0.

MD: ``compareAttribute` the name of the attribute to be compared with. _(currentAttribute_repeat)_` Expected: `compareAttribute the name of the attribute to be compared with. (currentAttribute_repeat)`

A solution to this needs to implement backtrack to see information about the characters before `_`. http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60compareAttribute%60+the+name+of+the+attribute+to+be+compared+with.+_%28currentAttribute_repeat%29_

A regex would have to match for a word boundary before the starting `_` character. `(?!\b)`

test cases: MD: ``` markdown `compareAttribute` the name of the attribute to be compared with. _(currentAttribute_repeat)_ `compareAttribute` the name of the attribute to be compared with. (_currentAttribute_repeat_) _em_word_with_underscores_ ``` expected:...

Another case: ``` markdown _one\_two_ __one\_two__ *one\*two* **one\*two** ```

does `opcache.save_comments=0` really safe some resources or improve speed? In general composition of markdown features could be implemented in a different way, but I do not think it is really...

Thank you for the detailed stats!