X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1643" "Thu" "2" "July" "1998" "23:53:18" "+0200" "Frank Mittelbach" "Frank.Mittelbach@UNI-MAINZ.DE" nil "39" "Re: Modules" "^Date:" nil nil "7" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id AAA28870; Fri, 3 Jul 1998 00:42:28 +0200 (MET DST) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <12.EA397726@listserv.gmd.de>; Fri, 3 Jul 1998 0:42:26 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 377192 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 3 Jul 1998 00:42:21 +0200 Received: from kralle.zdv.Uni-Mainz.DE (kralle.zdv.Uni-Mainz.DE [134.93.8.158]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id AAA21589 for ; Fri, 3 Jul 1998 00:42:19 +0200 (MET DST) Received: (from Ufrank@localhost) by kralle.zdv.Uni-Mainz.DE (8.8.8/8.8.8) id AAA28695 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 3 Jul 1998 00:42:20 +0200 (MET DST) X-Authentication-Warning: kralle.zdv.Uni-Mainz.DE: Ufrank set sender to latex3 using -f Received: (from latex3@localhost) by frank.zdv.uni-mainz.de (8.6.9/8.6.9) id XAA01307; Thu, 2 Jul 1998 23:53:18 +0200 References: <199806220631.QAA11602@ricetub.anu.edu.au> Message-ID: <199807022153.XAA01307@frank.zdv.uni-mainz.de> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: Date: Thu, 2 Jul 1998 23:53:18 +0200 From: Frank Mittelbach Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Modules Status: R X-Status: X-Keywords: X-UID: 2644 Hans Aberg writes: > Javier Bezos wrote: > > Renaming commands > > ~~~~~~~~~~~~~~~~~ > > Suppose someone is determined to study the internal latex code with the > > new naming scheme. He take the TeXbook and... surprise! The latex code is > > absolutely unintelligible. > > Richard Walker wrote: > >This was my reaction too. And the new names are often not transparent > >renamings of the original - as you point out, some are subtly > >different. You need to know not only the new names but you need to > >keep the implementations in mind too. > > I think the contrary: This is a very good, bold move, that is, if it can > be made to work. One then becomes independent of that old PlainTeX once for > all, and is free to build up an entirely new consistent logical structure. don't think i always disagree :-) i also think that neither Javier's nor Richard's fears are warranted. it is true that you would have a hard time to understand the code starting just from the TeX book. but this is true for any format that tries to do a bit more than plain TeX --- try understanding a few lines of lollipop or ConTeXT taken out of the middle (or even LaTeX2e without documentation and context) no i think that this you will have this problem always and the solution is that you provide a replacement book for the TeX book. > This will perhaps prepare for a new version of TeX, which can take care of > the new LaTeX3 structures efficiently. well yes and no. as long as you stay at least essentially with the token based interpreter then some things will not work. but yes this is something that can be hoped for. frank