On Wed, Nov 21, 2007 at 06:18:15PM -0500, Steve Sanbeg wrote:
Well, I'm not at all sure that my desire is unreasonable and your response, reasonable.
Very early in Steve's work, the issue was raised that one of the targets driving the effort of defining the language so that the parser could be reimplemented was the fact that it couldn't be a bad thing if people needing lightweight markup languages for other purposes could easily utilise mwtext for that.
My perspective is mostly, what is the data set tied to? I.e. a specification, a reusable component, or a set of applications.
Which data set? The language specification David seeks?
In that sense, it's probably not so much useful to create a parser to drop into other apps for its own sake, as that that would be complementary to less encumbered data.
More my point was that it seems more useful in the grand scale to make sure one's thinking about a language spec that's trimmable for smaller uses, than implementing an actual parser that can be dropped into other things... those other things are almost certainly not in PHP anyway. (If their implementers have any sense :-)
Cheers, -- jra