By having these different flavors in one place, it will make it much easier to keep small unintentional "drifts" from occurring between "dialects".
Ideally, the only differences would occur as related to syntax features that are implemented in one dialect, and not in another.
Another benefit is the ability to merge similar features that are implemented differently. For example, when Michel added footnote support to PHP Markdown Extra that was almost the same as the approach I had used in MultiMarkdown, it was easy for me to change the XHTML syntax so that they were compatible (though it appears they have drifted apart again...)
F- On Mar 23, 2008, at 8:13 AM, Tomas Doran wrote:
Yes, please also keep Text::MultiMarkdown. This is actually *much more* different to fletcher's MultiMarkdown than Text::Markdown is to Markdown.pl - as with my refactoring, MultiMarkdown is able to just overload / hook into Text::Markdown (as I've created the relevant hook points), as opposed to being a copy & paste of original markdown with bits stuck on the side.. (No offense meant here - I'm only able to do this as I'm *also* maintaining a fork of Markdown).Again, I'm aiming form *zero difference* between Text::MultiMarkdown and 'official' MultiMarkdown, except for bugs that I've fixed (so we shouldn't *expect* difference, and if it's found, and I don't have an explicit test in my distribution to cover it - it's a bug in my code and I *will fix it*).. My code does pass all of Fletcher's test suite, so I'm sure it's pretty similar. ;)As previously noted, s/MultiMarkdown/Markdown/g; s/Fletcher/John/g; in the paragraph above is also be true.Cheers Tom
--
Fletcher T. Penney
[EMAIL PROTECTED]
On two occasions I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able rightly to apprehend the kind of
confusion of ideas that could provoke such a question.
- Charles Babbage
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Markdown-Discuss mailing list [email protected] http://six.pairlist.net/mailman/listinfo/markdown-discuss
