Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 6 Jul 2003 18:51:36 +0200 Received: by mail.proteosys.com (8.12.9/8.12.2) with ESMTP id h66GpYPP007407 for ; Sun, 6 Jul 2003 18:51:34 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h66Gj2Gl017897; Sun, 6 Jul 2003 18:45:02 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C343DE.DCA35C00" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h66Bjwro010120; Sun, 6 Jul 2003 18:43:19 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 0455 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 6 Jul 2003 18:43:19 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id h66GhIpU011431 for ; Sun, 6 Jul 2003 18:43:18 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.184]) by relay.uni-heidelberg.de (8.12.9/8.12.9) with ESMTP id h66Givmp018146 for ; Sun, 6 Jul 2003 18:44:58 +0200 (MET DST) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19ZCdF-0001Wf-00 for LATEX-L@listserv.uni-heidelberg.de; Sun, 06 Jul 2003 18:44:57 +0200 Received: from [80.129.9.179] (helo=istrati.mittelbach-online.de) by mrelayng.kundenserver.de with asmtp (TLSv1:EDH-RSA-DES-CBC3-SHA:168) (Exim 3.35 #1) id 19ZCdF-0000sg-00 for LATEX-L@listserv.uni-heidelberg.de; Sun, 06 Jul 2003 18:44:57 +0200 Received: (from frank@localhost) by istrati.mittelbach-online.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id h66GhBZ26730; Sun, 6 Jul 2003 18:43:11 +0200 In-Reply-To: <200307061812.48589@KOMA020467> References: <16134.24630.894055.174261@zarniwoop.ms25.local> <16136.9181.487151.949600@istrati.mittelbach-online.de> <200307061812.48589@KOMA020467> Return-Path: X-Mailer: VM 6.96 under Emacs 20.7.1 X-OriginalArrivalTime: 06 Jul 2003 16:51:36.0710 (UTC) FILETIME=[DD0FB260:01C343DE] X-Authentication-Warning: istrati.mittelbach-online.de: frank set sender to frank@mittelbach-online.de using -f X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: -16.7 () IN_REP_TO,REFERENCES,USER_AGENT_VM,X_AUTH_WARNING Content-class: urn:content-classes:message Subject: Re: \input Date: Sun, 6 Jul 2003 17:43:11 +0100 Message-ID: A<16136.20895.431924.751931@istrati.mittelbach-online.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: \input Thread-Index: AcND3t0ony7WkLL+Tkqr0QrSElbgDg== From: "Frank Mittelbach" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4643 This is a multi-part message in MIME format. ------_=_NextPart_001_01C343DE.DCA35C00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > The TeX engine should because of (old) plainTeX files, but LaTeX = should use > \inputfile to implement its \input macro. if one is actually seriously looking at base language changes one has to = stop worrying about compatibility at one point or one will have to deal with = all kind of special cases forever. and a new engine would probably be subtly different anyway, so for processing old pain tex files one better use a = real TeX. yes i can get rid of the old syntax by simply disabling the commands so = from a macro format point of you i don't care, but it it is not going to make = the internal engine cleaner if all that kind of stuff is carried along = forever frank ------_=_NextPart_001_01C343DE.DCA35C00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: \input

 > The TeX engine should because of (old) = plainTeX files, but LaTeX should use
 > \inputfile to implement its \input = macro.

if one is actually seriously looking at base language = changes one has to stop
worrying about compatibility at one point or one will = have to deal with all
kind of special cases forever. and a new engine would = probably be subtly
different anyway, so for processing old pain tex = files one better use a real
TeX.

yes i can get rid of the old syntax by simply = disabling the commands so from a
macro format point of you i don't care, but it it is = not going to make the
internal engine cleaner if all that kind of stuff is = carried along forever

frank

------_=_NextPart_001_01C343DE.DCA35C00--