On 30/10/11 16:47, Happy Melon wrote:
I think that would make more sense as a tag extension (parse doesn't look like a good name, what about <wikidemo>?).
@Happy Melon: I think he wants a funtion which shows both parsed wikitext and the original source.
He intends to *build* such a structure, certainly; but I read the OP as saying he wanted to implement it via a template like {{demonstrate template}} [1] but with (just) the backend handled by a new parser function. I agree that you'd be better off/would avoid many of the problems given above by having a tag extension <wikidemo>{{foo|bar|baz=quok}}</wikidemo> that spat out its contents as a parameter to a customisable system message that read something like ""<code><nowiki>$1</nowiki></code> produces: $1"". If I remember the parse order of tag extensions verses parser function extensions right, that should work pretty much straight out of the box??
--HM
A tag hook spits out html, so he would output the content as literal, then recurse and output it again parsed.