X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1533" "Tue" "30" "June" "1998" "12:21:32" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "29" "Optimizing LaTeX" "^Date:" nil nil "6" 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 MAA14127; Tue, 30 Jun 1998 12:22:21 +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 <13.30AB491B@listserv.gmd.de>; Tue, 30 Jun 1998 12:22:19 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 374969 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Tue, 30 Jun 1998 12:22:15 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id MAA21068 for ; Tue, 30 Jun 1998 12:22:13 +0200 (MET DST) Received: from [130.237.37.134] (sl108.modempool.kth.se [130.237.37.134]) by mail.nada.kth.se (8.8.7/8.8.7) with ESMTP id MAA29461 for ; Tue, 30 Jun 1998 12:22:06 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se (Unverified) References: <199806230127.LAA12452@ricetub.anu.edu.au> <199806220631.QAA11602@ricetub.anu.edu.au> <199806271853.UAA29351@frank.zdv.uni-mainz.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199806281358.XAA16592@ricetub.anu.edu.au> Date: Tue, 30 Jun 1998 12:21:32 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Optimizing LaTeX Status: R X-Status: X-Keywords: X-UID: 2615 If LaTeX now is so slow one could pick up Richard Walker's idea, and develop the docstrip facility into an optimizing compiler: > I'd like to push forward my earlier >idea of docstrip writing out a file containing a list of macros defined, >macro documentation or whatever, in a form that can be easily used by >smart editors. So, for example, if the source file contains a command \newcommand{\foo}[9]{def}, then the docstrip writes out \define#1#2#3#4#5#6#7#8#9{def} in the sty file, plus perhaps a file \newcommand{\foo}[9] with document processors can use. The command \define would check that \foo has not been defined before, but perhaps one can optimize further, so that this check is not done every time the file is executed. (Say perhaps when a building format file: Then the check would be done while building the format, but not when loading the format.) The idea of docstrip as an optimizing compiler would enable to do develop with relatively high level commands. One could also think of a special file with online help: A command named \foo has a command \foo: with information about the command which is put in a special file. Then that command and its file need to be processed in the usual typesetting, only when one needs say the online help, so it does not burden the speed of LaTeX. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: