james.robinson wrote:

patch to allow ParserFunctions to work with other parser objects

Attached:

You can clone $wgParser to produce an independent local parser with all the extensions
registered, this has the advantage of avoiding setup overhead.

james.robinson wrote:

That did not occur to me. I'll test that out. Thank you kindly.

Your suggestion is still a good one, and we may well implement something similar to it. My
only reservation is that extension registration is best done in firstCallInit() rather than
clearState(). That would require adding a new hook. Hook-based registration is better than
what we have now, but ideally I would like to have the registered extension list cached as
a whole, rather than initialised by running code from every extension on every web request.

robchur wrote:

Reopening; no indication of how this was fixed, and I see no relevant commits.

(In reply to comment #5)

Reopening; no indication of how this was fixed, and I see no relevant commits.

Comment #2 'fixes' this.