[ANN] PHP Markdown 1.0b5

[Lou Quillio]

On May 3, 2004, at 6:30 AM, Michel Fortin wrote:

> What I worry about is propagating the changes John makes to his Perl 
> version.

> Is there any other reasons to enclose all the code into a class? If 
> plugins could be made by adding a small plugin class in the file 
> simply calling the Markdown function, would it be as good? I guess I 
> need some feedback on these two questions before I decide what to do.

I suppose it's premature, as you say.  I battered PHP Markdown into a 
class, too, but haven't shared it because I don't want to be 
responsible for maintaining it (plus it's sloppy).

For the time being it makes more sense to uniquely name all variables 
and wrap markdown() alone in a class.  Hadn't thought of that.  I'll 
try it that way.

In the end, though, I think PHP Markdown will be more widely used if 
it's completely self-contained.  Thanks for all your work.

LQ