X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["756" "Wed" "8" "October" "1997" "14:42:51" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "15" "Re: Extended include" "^Date:" nil nil "10" 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.5/8.8.5) with ESMTP id QAA01354; Wed, 8 Oct 1997 16:46:50 +0200 (MET DST) Received: from lsv1.listserv.gmd.de by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <15.25BC1A44@listserv.gmd.de>; Wed, 8 Oct 1997 16:46:11 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 210622 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Wed, 8 Oct 1997 16:46:02 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.7/8.8.7) with ESMTP id QAA23724 for ; Wed, 8 Oct 1997 16:45:40 +0200 (MET DST) Received: from [130.237.37.74] (sl54.modempool.kth.se [130.237.37.74]) by mail.nada.kth.se (8.8.7/8.8.4) with ESMTP id QAA03680 for ; Wed, 8 Oct 1997 16:45:39 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se References: <9083-Mon06Oct1997144554+0100-s.rahtz@elsevier.co.uk> <3997-Mon06Oct1997095918+0100-s.rahtz@elsevier.co.uk> <199710062136.WAA00429@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: <199710071922.UAA00483@frank.zdv.uni-mainz.de> Date: Wed, 8 Oct 1997 14:42:51 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Extended include Status: R X-Status: X-Keywords: X-UID: 2397 Frank Mittelbach : >In fact for some prototype kernel (long time ago) I implemented a >scheme that always used two aux files: one to read from and one to >write to. The advantage was that a) less files and b) much better >control in error situations, ie in case your run ended in the middle >latex would not use the file that was only partly written but the one >that was fully written last time. This is a problem with the Textures flush (or was it flash?) mode: So I think this idea should be taken up again. Hans Aberg * AMS member: Listing * Email: Hans Aberg * Home Page: