Steve Bennett wrote:
I'm picturing 4 passes:
- Preprocessor: substitute templates (and parser functions?) into the text
stream
And custom tags.
Actually I have a strong preference for using extractTagsAndParams as a *public* function in order to extract extension tags rather than adding parser Hooks.
- Parser: build an AST by reading the text stream
- Contexter: manipulate the AST, disambiguating ''' and '' by using the
built context. Tidy up nested lists. 4) Renderer: convert the AST into XHTML or whatever.