References: <m0wdxiT-000OVnC@dcarlisle.demon.co.uk>
            <199706181237.MAA00063@ew160061.nets.de.eds.com>
            <199706191620.RAA07046@fell.open.ac.uk>
            <33A97714.34BAB20B@vvv.vsu.ru>
Mime-Version: 1.0 (generated by tm-edit 7.95)
Content-Type: text/plain; charset=US-ASCII
Message-ID:  <199707071846.UAA07932@puma.npc.de>
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
In-Reply-To:  <33A97714.34BAB20B@vvv.vsu.ru>
Date:         Mon, 7 Jul 1997 20:46:21 +0200
From: Joachim Schrod <jschrod@ACM.ORG>
Sender: Mailing list for the LaTeX3 project
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
To: Multiple recipients of list LATEX-L
              <LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE>
Subject:      Re: [Bug Report] Problem with INPUTENC package and TOC files.
Status: R

>>>>> "VV" == Vladimir Volovich <TeX@VVV.VSU.RU> writes:

[Yeah, I know, it's weeks ago. But then, I don't come to read TeX
mailing lists so often nowadays. ;-) ]

VV> [ But there is really only one correct parser---TeX ;-) ]

No. There exist other(s). Besides those parsers mentioned here, that
often parse only a subset of TeX, I've written a full system, called
TLSI (TeX Language Specification Interpreter). It's described in
TUGboat, in the St.Barbara proceedings.

Of course, as TeX doesn't have much syntax anyhow (at least not in the
sense normal CS folks think of syntax), that doesn't buy you much.
What one really would need are hooks in the yet-to-be-written
typesetting and data engine.

Cheers,
        Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod                                  Email: jschrod@acm.org
Net & Publication Consultance GmbH              Tel.:  +49-6074-861530
Roedermark, Germany                             Fax:   +49-6074-861531