X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2663" "Sun" "2" "March" "1997" "11:39:00" "-0600" "Randolph J. Herber" "herber@DCDRJH.FNAL.GOV" nil "55" "Re: Shortref mechanism" "^Date:" nil nil "3" nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.5/8.8.4) with ESMTP id SAA32050; Sun, 2 Mar 1997 18:40:33 +0100 (MET) Received: from listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <8.AC6E7E40@listserv.gmd.de>; Sun, 2 Mar 1997 18:40:32 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 107795 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 2 Mar 1997 18:40:30 +0100 Received: from dcdrjh.fnal.gov (dcdrjh.fnal.gov [131.225.103.66]) by relay.urz.uni-heidelberg.de (8.7.6/8.7.4) with SMTP id SAA14457 for ; Sun, 2 Mar 1997 18:40:28 +0100 (MET) Received: (from herber@localhost) by dcdrjh.fnal.gov (950413.SGI.8.6.12/950213.SGI.AUTOCF) id LAA27835; Sun, 2 Mar 1997 11:39:00 -0600 Message-ID: <199703021739.LAA27835@dcdrjh.fnal.gov> Reply-To: Mailing list for the LaTeX3 project Date: Sun, 2 Mar 1997 11:39:00 -0600 From: "Randolph J. Herber" Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Shortref mechanism Status: R X-Status: X-Keywords: X-UID: 1847 The following header lines retained to affect attribution: |Date: Sun, 2 Mar 1997 13:48:57 +0100 |From: Hans Aberg |Subject: Re: Shortref mechanism |Frank Mittelbach wrote: |>The above means that the shortref mechanism either has to be fully |>expandable or that one can't use it to produce glyphs that might play |>a part in ligature or kerning tables. | I cannot follow the details in your reasoning, but I can note that with |deterministic parsing, the method generally used in LaTeX, conditional ^^^^^^^^^^^^^ ^^^^^^^ ^^^^^^^^^^^ |parsing have such limits. ^^^^^^^ | But with non-deterministic parsing more general things can be done: ^^^^^^^^^^^^^^^^^ | For example, I just made a definition command that can produce commands |having optional arguments; in this general approach, I had to switch from |LaTeX style deterministic parsing to non-deterministic parsing. ^^^^^^^^^^^^^ ^^^^^^^ ^^^^^^^^^^^^^^^^^ ... | Hans Aberg To someone that has written several small compilers and has studied automata theory at the doctorate level, your word choice as high-lighted above is quite jarring. By using a power automaton, a non-deterministic automaton can be reduced to a deterministic automaton. Therefore, one does not gain any power of expression by using a non-deterministic automaton, rather one only gains compaction of the description. I believe that what you intended is the distinction of context free and context sensitive languages. From what I have read in the TeX book, the tokenizer of TeX is context sensitive with a single character look-ahead and the TeX language based on the recognized tokens is context free. It is a significant change in the behavior of the TeX language to change it from being context free to being context sensitive. But, it may be a necessary change. Most modern computer languages are context sensitive with a single token look ahead. A few look ahead two tokens in some situations. I imagine that some look ahead three tokens. Parser generators for single token look ahead readily are availed. What you are proposing is a change from zero token look ahead to one token look ahead. Randolph J. Herber, herber@dcdrjh.fnal.gov, +1 630 840 2966, CD/OSS/CDF CDF-PK-149O Mail Stop 234 Fermilab, Kirk & Pine Rds., P.O. Box 500, Batavia, IL 60190-0500. (Speaking for myself and not for US, US DOE, FNAL nor URA.) (Product, trade, or service marks herein belong to their respective owners.) N 41 50 26.3 W 88 14 54.4 and altitude 700' approximately, WGS84 datum.