Good question, to which the fast answer is "no".
Someone capable of documenting how to turn SLIF into THIF might be
better off rewriting the upper layers in some other form, such as pure C
or C++, Python, better Perl, etc., etc. I'm doing that, in C and Lua,
as the Kollos project. (I'm overloaded, so Kollos won't happen
quickly.) This is following the principle that, when the code is not at
all clean, you rewrite first and THEN document. It would also be more
fun for the rewriter, because it would allow the rewriter to experiment
with the language/interface of their choice. (As to why the current
XS/Perl implementation is a mess, the answer is that it evolved
incrementally in response to the demand for new features, and in the
face of a strict requirement that every change had to preserve
compatibility, even with obsolete interfaces.)
-- jeffrey
On 08/21/2014 04:48 PM, Ron Savage wrote:
Anyone documented this process?
--
You received this message because you are subscribed to the Google
Groups "marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "marpa
parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
