Rowan Collins wrote: Neither of your suggestions would fix something something like this: {{template1||para1={{template2||para=hah, you're screwed!}}}} (or would it?) Better to fix the parser properly... Timwi

On Wed, 28 Jul 2004 10:41:18 -0700 (PDT), David Iberri <diberri(a)yahoo.com> wrote: So they do... Question is, does anyone know how that *does* work? [Parser.php is more than a little, um, opaque...] -- Rowan Collins BSc [IMSoP]

On Wed, 28 Jul 2004 20:52:24 +0100, Rowan Collins <rowan.collins(a)gmail.com> wrote: I haven't looked at it (and don't have time at this exact moment) but I imagine it's something like this: Keep track of how deep you are nested within the [['s, and treat the | characters differently according to context. If you're at the top level, a | character is a delimiter for that level, but if you're already nested inside another [[ level (i.e. you're inside a link) then treat the | character according to the piped-link interpretation. Look for ]]'s to know when you should pop back out to the previous level/context. -Bill Clark

On Wed, 2004-07-28 at 23:30 +0100, Timwi wrote: Not necessarily- it's more or less the fastest way to do this with a regex-based parser like the current MediaWiki one. The second call ist not expensive. Searches the entire text though.. -- Gabriel Wicke

Bill Clark wrote: Hello, That will be the way to do it using a tokenizer. Unfortunatly the tokenizer is disabled for performance issue. -- Ashar Voultoiz

On Thu, 2004-07-29 at 19:59 +0000, Ævar Arnfjörð Bjarmason wrote: The code exists in php, but is a few times slower than the current parser. That tokenizer also handles only a few of [count > 20] passes. I'm currently writing a new parser using BisonGen (builds both a C python module and a pure python parser) that handles the entire parsing in one step. The C version also performs very well (0.014 seconds vs. 0.17 seconds for the pure python version). The output will be a DOM object tree, includes and the like will be handled by manipulating that tree before dumping it as [insert your favourite format here]. Where feasible, this parser also supports the current Moin syntax additional to the MW one, it's intended to work with Moin of course (which has a relatively clean design and profits from the python infrastructure). Some more details at http://moinmoin.wikiwikiweb.de/NewWikiParser. -- Gabriel Wicke