if you want to see a document made with it, then see here or a better place
not sure what it really does.
but there's an easy way to find out!
The following is a {code ...} region, presumably for lisp.
(define (foo) (whatever)) ;; how verbatim is {code} (didn't this make <p> b4???) ;; following two lines are blank in source.(define (bar) (somethingelse)) ;; next two lines have {comment} (define (qux) (nothing))
should write a new lexical environment for C, since C uses {}s frequently:
double pow(double base, int exp) { int t, bit = 1; int square = base; double result = 1.0;while (bit <= exp) { if (bit & exp) result *= square; bit = bit << 1; square *= square; } return result; }
the {evalsto} directive is for lisp examples like (+ 1
2)-->3
. this is fine (though not very pretty), but way cooler
would be a macro where you don't have to give the right hand side
because it computes it. Finally, also interesting would be a
directive that allowed one to show a piece of markup code, and the
effect of executing it side by side.
as noted in [scheme] la de da da. you can link random
text to arbitrary URLs. here is some math . Bibs and end notes also supported, but
not really used in this document.
testing postscript file inclusion:
the {ps filename} directive takes any postscript file and renders it with antialiasing, and includes it as a gif file. specialized directives that draw diagrams of example data structures (eg box-n-pointer with dot) are planned.
you can define simple (argumentless) macros with {def name
{body text}}
thus simple simple simple.