Markup Macro Processor

{/de}

The cleverness is all in the (non obvious) Javascript (which colors the headline blue when the text is hidden, red when it’s showing). But you (or me) has to figure it out only once, and enter it only once. Then to use it you put it in a file – say, droptext.i – and in your source have the macro call {import droptext.i/} . The import macro will include it with your source, unless it’s already been imported  – import will not include multiple copies.

People can use droptext without knowing anything about Javascript. Incidentally, the droptext can be any content including nested calls to droptext.

The script above might seem a problem because MMP treats curly parentheses specially. There is, however, an easy way around this. MMP does not give special attention to open curly parentheses followed by a blank, nor to closed curly parentheses preceded by a blank. The Javascript above has been padded with blanks to avoid such special attention.

But of course there’s a lot more to know about MMP if you want to author macros, not just use them. For a start, there’s built-in ‘system’ macros that don’t work by string substitution. An example is the  + macro which adds its arguments, so for example {+ 3 5 7} evaluates to 15 . Especially useful is the replacement macro r which applies regular-expression based substitutions to its body (using Java’s conventions). Thus

{r William Bill}I’m William Wadge{/r}

expands to

I’m Bill Wadge

Another complication is the definition macro: de is not the basic system macro, it has a definition, but treats $ specially. The system definition macro : does not do this, it uses pseudo macros for the arguments (e.g.{1/}) and body ({/_}). The page macro definition becomes

{” : page}

{html}

{_/}

{/”}

One subject which is touchy with all macro processors is quoting – blocking expansion temporarily. The above definition is a call to the quote macro, which calls its first argument with the body quoted. We don’t want to try to expand {1/} and {_/} until we have an actual argument and body.

Another complication is scripting. MMP does not have an escape to a conventional scripting language. Possibly a mistake. Instead, it has macros with side effects that can be combined into scripts. This is not as bad as it sounds because MMP allows macros with multiple bodies that are evaluated in sequence. And one can define macros for conditionals, loops, switch statements etc.

There is, however, one source of trouble that I can’t fix, one that is found in any system that introduces layers of abstraction. The trouble is with error handling. What if you’re using a lot of high-level macro calls and you make a mistake? MMP is good at detecting errors but it handles them at the lowest level. What we need to do is intercept them and convert them to messages that make sense at a higher level. I still don’t know of any conventions for doing that.

There’s also some good news. MMP integrates the intensional approach to versioning we applied to web sites. Macros can have separate versions defined separately. As a super simple example, suppose we define

{de greet}Hello{/greet}

and suppose we also have French and Spanish versions of our website. Then we can separately (but in the same file) define French and Spanish versions of our greet macro:

{de greet lang:fr}Salut{/greet}

{de greet lang:sp}Hola{/greet}

Then the call {greet/} evaluated in a context where lang:fr holds produces Salut, and in a context where lang:sp we get Hola. If lang has some other value, or has no value, we default to Hello. Notice that when we call greet we don’t have to specify the versions, the macro picks that up from the ‘atmosphere’.

As I said, MMP has been implemented by Paul Swoboda and myself in a few thousand lines of Java. Although it has been implemented using mindless string copying it’s fast enough to use as a web language. My Uvic colleague Dr Alex Thomo installed it in a Java servlet. Demands come in for .mmp files, the macros are expanded, and the resulting html text generated is sent back as the response.

I haven’t put it on github yet so if you want to try out MMP, mail me at wwadge@me.com.