Seemingly working (OK w/ William the Conqueror + lots) input side

I might fork to a similar but tighter C++ implementation at this point
and come running back here if that proves even more of a headache.

Python's dynamic binding (and typing) leave a lot to be desired as to
known vs. unknown points of failure, and history data corruption /
loss upon rewrite/transformation due to some corner case in the code
that was never exercised or tested explicitly. Such a problem would be
totally unacceptable and would be far too easy to skate-by
unnoticed. I can't test every existing or future valid character
history language element's translation into the parser without
manually inspecting and verifying every single character's parse; I
have to rely upon invariants. Python doesn't feel right for this.

Unfortunately, the C++ version is going to look similar (just
seemingly more complicated to those unfamiliar w/ C or C++) in
implementation, as I don't foresee that using normal C++ tools like
quex/flex and, say, even a hand-coded predictive LL(1) parser is
necessary or desired for the pure simplicity of this "language."

Will he fork it or won't he?  We'll have to see.