Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f16MPkH20289 for ; Tue, 6 Feb 2001 23:25:46 +0100 Received: by webgate.proteosys.de (8.11.0/8.11.0) with ESMTP id f16MPjd06422 . for ; Tue, 6 Feb 2001 23:25:45 +0100 Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f16MPj717526 for ; Tue, 6 Feb 2001 23:25:45 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0908B.BFDA9100" Received: from mailgate2.zdv.Uni-Mainz.DE (mailgate2.zdv.Uni-Mainz.DE [134.93.8.57]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id XAA26177 for ; Tue, 6 Feb 2001 23:25:44 +0100 (MET) Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f16MPi717518 for ; Tue, 6 Feb 2001 23:25:44 +0100 (MET) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <1.945D12FA@mail.listserv.gmd.de>; Tue, 6 Feb 2001 23:25:39 +0100 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 489174 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 6 Feb 2001 23:25:41 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA16062 for ; Tue, 6 Feb 2001 23:25:40 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA26960 for ; Tue, 6 Feb 2001 23:25:40 +0100 Received: from musse.tninet.se (musse.tninet.se [195.100.94.12]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with SMTP id f16MPeu16851 for ; Tue, 6 Feb 2001 23:25:40 +0100 (MET) Received: (qmail 29540 invoked from network); 6 Feb 2001 23:25:38 +0100 Received: from delenn.tninet.se (HELO algonet.se) (195.100.94.104) by musse.tninet.se with SMTP; 6 Feb 2001 23:25:38 +0100 Received: from [195.100.226.137] (du137-226.ppp.su-anst.tninet.se [195.100.226.137]) by delenn.tninet.se (BLUETAIL Mail Robustifier 2.2.1) with ESMTP id 406673.498337.981delenn-s1 for ; Tue, 06 Feb 2001 23:25:37 +0100 In-Reply-To: <14976.19977.570637.825825@istrati.zdv.uni-mainz.de> References: Return-Path: X-Sender: haberg@pop.matematik.su.se (Unverified) Content-class: urn:content-classes:message Subject: Re: More template experience Date: Tue, 6 Feb 2001 23:24:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Hans Aberg" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3732 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0908B.BFDA9100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable At 18:39 +0000 2001/02/06, David Carlisle wrote: > each with a brace group (\csname doesn't mind category 1 and = 2 > characters), since even an ingenious fool has work very hard to get = braces > mismatched in arguments, whereas with the current naming scheme At 20:18 +0100 2001/02/06, Frank Mittelbach wrote: >this is weird :-) and i thought my learning days on TeX the programs = have been >over. > >even > > \expandafter\show \csname ab{cd\endcsname > >does work. TeX uses the character catcodes to tokenize the input, but if the lexer finds a macro name, it must do an additional table lookup in order to = stamp an additional, internal token number (not described in the TeX book) for the parser, evidently, as different macros can obey a different syntax. But my guess is that both the lexer regular words syntax and the parser LALR(!) (?) syntax are fixed, only the character catcodes and the macro internal codes can change. (So why is TeX's syntax then commonly called "extensible" if both grammars are fixed?) Has this TeX parser grammar been published somewhere? Hans Aberg ------_=_NextPart_001_01C0908B.BFDA9100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: More template experience

At 18:39 +0000 2001/02/06, David Carlisle = wrote:
> each <name_i> with a brace group (\csname = doesn't mind category 1 and 2
> characters), since even an ingenious fool has = work very hard to get braces
> mismatched in arguments, whereas with the = current naming scheme

At 20:18 +0100 2001/02/06, Frank Mittelbach = wrote:
>this is weird :-) and i thought my learning days = on TeX the programs have been
>over.
>
>even
>
>  \expandafter\show \csname = ab{cd\endcsname
>
>does work.

TeX uses the character catcodes to tokenize the input, = but if the lexer
finds a macro name, it must do an additional table = lookup in order to stamp
an additional, internal token number (not described = in the TeX book) for
the parser, evidently, as different macros can obey a = different syntax.

But my guess is that both the lexer regular words = syntax and the parser
LALR(!) (?) syntax are fixed, only the character = catcodes and the macro
internal codes can change. (So why is TeX's syntax = then commonly called
"extensible" if both grammars are = fixed?)

Has this TeX parser grammar been published = somewhere?

  Hans Aberg

------_=_NextPart_001_01C0908B.BFDA9100--