On Wed, Feb 26, 2014 at 12:05 PM, Jeffrey Kegler
<jeffreykeg...@jeffreykegler.com> wrote:
> Looking at it, I noticed there seems to be no test suite.  Test suites are
> worth the trouble.

Test suites for SGML parsing are are _hard_. I've tried getting one
going using "vanilla" Docbook, and I can't quite get my thoughts in
place to know what exactly I want the API to even look like. The plan
is to have a test suite that roundtrips between two or more various
SGML applications (maybe XML and Wikimedia or something).

Also, test suites in general are hard. They assume that the person
writing the tests is smarter than the person writing the code. I could
do some Test::LectroTest generation of ... something, and at least
have some "doesn't die" tests.

> Perhaps related, a "target app" might help.  Except that it should be
> something you care about, don't be fussy about this -- all that is necessary
> is that it exercise what you're developing in some way.

The target app is mostly "gloria", my work-in-progress log-groveler. I
want it to be able to comprehend any SGML application, and I want a
command language to instruct it on how to attach semantics to the
parsed syntax. For XML, the obvious route is via XPath and XSD (and
maybe XSLT), and for structured text of other kinds (that isn't
covered by an existing module, like JSON or YAML), Marpa's SLIF itself
is probably the obvious route. For SGML, I think I'm going to need to
generalize XPath, and that's why my main goal is reproducing an API
that looks and feels a bit like Marpa::R2::HTML, because the end-user
inputs to _that_ API are quite XPath-like.

Thanks, also, for linking MarpaX::xPathLike the other day. I think
some reading of both the source and docs is going to be required
there.


--
Paul

-- 
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 marpa-parser+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to