[e-lang] Convert Walnut to MediaWiki

[Mark S. Miller]

James Graves wrote:
> Can we create an command-line option for updoc so that it can be given a 
> file which contains code prefixed to anything being tested?
> 
> So you just have:
> 
> updoc.e -p prefix.e http://foo.com/vector.html
> 
> Where the file prefix.e contains:
> 
> ? pragma.syntax("0.9")

If we decide this is a good idea, it would certainly be easy to do. However, 
how would someone looking at the page know that this is what they need to do?

I'm wondering whether MediaWiki has any kind of transclusion feature like 
Tyler's CapWiki. It is a way for one page to include content from another 
page, or from a section of another page. This way, we could have standard 
updoc header text in one place, and have all other pages transclude it.

Transclusion would also give us an adequate solution to the Walnut problem. 
The linearized Walnut could just be a list of transclusions of all the Walnut 
content pages.



> Alternatively, we can create a robot that periodically scans the wiki 
> for pages containing E code.
> 
> If it doesn't find a pragma statement, it will add one.
> 
> This can be done remotely (over the web interface) or by something that 
> has direct access to the MediaWiki database.
> 
> There are already bunches of bots that do work on Wikipedia:
> 
>    http://en.wikipedia.org/wiki/Wikipedia:Bots

Cool! Once we solve the updoc security problem, perhaps we could make an 
updoc-testing bot -- automatically annotating the pages with the testing results.


-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM