Received: via tmail-4.1(11) (invoked by user schoepf) for schoepf; Mon, 6 Mar 2000 23:09:09 +0100 (MET) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id XAA28258 for ; Mon, 6 Mar 2000 23:09:00 +0100 (MET) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF87B8.9862B080" Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id XAA08803 for ; Mon, 6 Mar 2000 23:09:00 +0100 (MET) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <5.3CCED5FF@mail.listserv.gmd.de>; Mon, 6 Mar 2000 23:07:41 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 452988 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 6 Mar 2000 23:06:20 +0100 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA14507 for ; Mon, 6 Mar 2000 23:06:19 +0100 (MET) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id XAA21850 for ; Mon, 6 Mar 2000 23:08:55 +0100 Received: from nag.co.uk ([62.232.54.10]) by relay.uni-heidelberg.de (8.9.3+Sun/8.9.3) with ESMTP id XAA09310 for ; Mon, 6 Mar 2000 23:06:19 +0100 (MET) Received: (from davidc@localhost) by nag.co.uk (AIX4.2/UCB 8.7/8.7) id WAA14050; Mon, 6 Mar 2000 22:05:01 GMT In-Reply-To: <200003062147.WAA01565@kammer.uni-hannover.de> (message from Reinhard Kotucha on Mon, 6 Mar 2000 22:47:47 +0100) References: <200003052035.VAA01735@kammer.uni-hannover.de> <200003062147.WAA01565@kammer.uni-hannover.de> Return-Path: x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil]["911" "Mon" "6" "March" "2000" "22:05:01" "GMT" "David Carlisle" "davidc@NAG.CO.UK" nil "19" "Re: bop-hook" "^Date:" nil nil "3" nil "bop-hook" nil nil nil]nil) Content-class: urn:content-classes:message Subject: Re: bop-hook Date: Mon, 6 Mar 2000 23:05:01 +0100 Message-ID: <200003062205.WAA14050@nag.co.uk> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "David Carlisle" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 3543 This is a multi-part message in MIME format. ------_=_NextPart_001_01BF87B8.9862B080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > I do not want to have the code in a package. This would > result in a patch. A hook wouldn't blow the kernel up, the begin > document hook is only a few lines of code. even if it was 1 line of code (which actually it is as there is a begin page hook, but it disables itself after the first time, so it can be advertised as \AtBeginDvi) you would want it as a package. making changes to the kernel to add new features causes so many problems for portability, we still now have to deal with the affects of allowing \MakeUppercase to work on section titles: a change made 3 (4?) years ago. A package, especially one that contains a single line of code is far easier to manage in terms of document portability. Of course technically there is no reason for this: anyone who can download a package can download latex/base and make a new format but real life unfortunately doesn't follow logical rules. David ------_=_NextPart_001_01BF87B8.9862B080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: bop-hook

>  I do not want to have the code in a = package.  This would
> result in a patch.  A hook wouldn't blow = the kernel up, the begin
> document hook is only a few lines of = code.

even if it was 1 line of code (which actually it is as = there is a begin
page hook, but it disables itself after the first = time, so it can be
advertised as \AtBeginDvi) you would want it as a = package.

making changes to the kernel to add new features = causes so many
problems for portability, we still now have to deal = with the affects of
allowing \MakeUppercase to work on section titles: a = change made 3 (4?)
years ago. A package, especially one that contains a = single line of code
is far easier to manage in terms of document = portability.

Of course technically there is no reason for this: = anyone who can
download a package can download latex/base and make a = new format
but real life unfortunately doesn't follow logical = rules.

David

------_=_NextPart_001_01BF87B8.9862B080--