From: Artem <ne...@gm...> - 2008-06-05 16:36:10
|
Waylan Limberg wrote: > Don't worry to much about breaking old extensions. If you refactor the > inline patterns (as noted below), extensions will need to be updated > anyway. Just make sure your changes are actually useful, not just a > new color for the bikeshed. > > Ok. >> - There is something to do with Inline patterns, I didn't decide yet >> what is the best way to fix it. That was discussed in list and there are >> some ideas. I thought of writing syntax/lexical parser instead of >> current Inline Patterns mechanism, but I think it'll be a bit slower. >> >> - I'll try to boost performance, I think choosing the right way of >> inline patterns modification is the best way to boost Markdown. >> > > I agree. I'd really encourage you to spend the most time on the inline > pattern issue. That's where markdown.py needs the most help IMO. > Yep, I already understood it. > Just be sure to update any extensions in the repo that you break. Feel > free to check with me on any of them as I wrote most of them. > Ok, thanks. |