that when processing Lines in compile_document().
2. Add some test cases for [footnote] links showing up in
random places.
3. In `dumptree()`, show the `ident` string ,if any, associated
with a given block.
`compile()` out into `compile_document()` (toplevel; split documents
into html, style, sourcecode, extracts all footnotes) and `compile()`
(compiles all content, but does not process html blocks or footnotes)
Not perfect: I should not need the SOURCE object type -- I should be
able to simple compile a block of source and append that source onto
the top-level paragraph list, but when I do that I end up with memory
leaks and test failures.
--enable-amalloc) replaced malloc and its ilk with
versions that attempt to maintain a linked list of
allocated blocks that can be printed to stderr with
the `adump()` function.
2. Clean up a couple more places where I leak memory
during the first level parse.
3. tweak cstring.h to try to chase down places where
the C compiler might optimize EXPAND() into producing
broken code.
1. Officially expose mkd_compile(), mkd_cleanup(),
mkd_generatehtml().
2. Internally use the new Document structure, which
hold the markup and (optionally) header information.
3. Support ``--enable-<foo>`` during configure.sh
* change --with-dl-tag to --enable-dl-tag.
* add --enable-pandoc-header to support pandoc headers.
that does the work; it's now __mkd_compile() [setup + compile], which
compiles the input, sets up a MMIOT, then returns a pointer to the
compiled Paragraph tree, and __mkd_cleanup() which cleans up all of
the data structures created by __mkd_compile().
Also add a title argument to mkd_dump() so I can show the tree rooted
at a title (the filename of the input file, or `stdin` if none was
given.)