Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id o8G9iYML009638 for ; Thu, 16 Sep 2010 11:44:37 +0200 Received: (qmail 3924 invoked by alias); 16 Sep 2010 09:44:29 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 16 Sep 2010 09:44:27 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx060) with SMTP; 16 Sep 2010 11:44:27 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o8G9g6df010104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Sep 2010 11:42:06 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o8G8kaPR028362; Thu, 16 Sep 2010 11:42:28 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 450146 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 16 Sep 2010 11:42:28 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id o8G9gSh1009302 for ; Thu, 16 Sep 2010 11:42:28 +0200 Received: from oberon.open.ac.uk (oberon.open.ac.uk [137.108.141.46]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o8G9fkhX009887 for ; Thu, 16 Sep 2010 11:41:50 +0200 X-IronPort-AV: E=Sophos;i="4.56,375,1280703600"; d="scan'208";a="51807760" X-Disclaimed: 1 Importance: Normal X-Priority: 3 (Normal) References: <19109.1284579373@cl.cam.ac.uk> <4C9122A1.4060008@morningstar2.co.uk> <4C91239B.2040301@morningstar2.co.uk> <4C912F95.70503@morningstar2.co.uk> , <19601.55875.121644.485219@morse.mittelbach-online.de> MIME-Version: 1.0 X-Mailer: Lotus Domino Web Server Release 8.5.2 HF16 August 30, 2010 X-MIMETrack: Serialize by HTTP Server on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 16/09/2010 10:42:07, Serialize complete at 16/09/2010 10:42:08, Itemize by HTTP Server on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 16/09/2010 10:42:08, Serialize by Router on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 16/09/2010 10:42:08 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id o8G9gSh1009303 Message-ID: Date: Thu, 16 Sep 2010 10:42:07 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Chris Rowley Subject: Re: e-TeX low-level expertise needed Re: Allocation of registers To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <19601.55875.121644.485219@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p6i75npGen84eVAEFK/syJmFuaL1OLtauwJ5R/kaZ9HAe8peGX1DeqJL7BW4 1X28hmBsSaikXt0ebYfUaHmtXkk7HChP+4IT8t5foOuRzC8vyH8YP07l+7OgkY63m+qRZCiPVOZg mL0OA==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6386 No intention to be 'hard on Peter'. Merely a suggestion that, at least in the documentation, something could be done to clarify this. Whether this is in The Manual or not depends for whom that manual is intended. TeX itself is always quite good at telling us, somewhere, when tokens are effectively ignored. More generally, why is there suddenly some 'subjective moral standard' about what a software system should or need not do? A vaguer question: Is the level of the relatively efficiency of the types of register of any practical consequence in the 21st century? chris -----Frank Mittelbach wrote: ----- To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE From: Frank Mittelbach Date: 16/09/2010 09:50 Subject: Re: e-TeX low-level expertise needed Re: Allocation of registers Chris,  > >>  > I did a few tests. As the e-TeX manual says, you can't \insert beyond  > 254. \insert255 gives the special 'You can't \insert255' error (as  > without e-TeX), and anything higher is a bad register code. (The  > {} seems to vanish.)  > >>  >  > Ah, but is that vanish b: or vanich c: :-) ??    > I think we should be told!  I suspect b: (ie the tokens in are  > never processed at all) but what a waste of tokens...!!  And the error  > message or something should point this out to B.L.Euser you shouldn't be too hard on Peter (who I guess wrote that code) -- if eTeX replies with a "bad register code" error then I think that is good enough even if perhaps not the best error message you can get. And frankly what happens after a severe error is kind arbitrary so that it really doesn't matter much in my opinion whether you will be told in the manual exactly how the program recovers. So in my opinion, if eTeX manual states that \insert only works on 0-254 and then also goes and generates an error if you try differently then it does all that is needed. A consequence for us seems to me that indeed we can't do much more than reserve a range for use with inserts at least while we live in coexistance with code that uses inserts.  The boundary is reserving all lower registers, but that is most certainly overkill and as the higher registers are supposed to be less efficient we should probably not waste too much of the main registers. For now I think providing an additional 30 inserts is the right level frank --------------------------------------------------------------------------- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302)