X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1647" "Fri" "3" "July" "1998" "20:14:36" "+0200" "Frank Mittelbach" "Frank.Mittelbach@UNI-MAINZ.DE" nil "42" "Re: First experience with xr under L3PL" "^Date:" nil nil "7" 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 WAA16852; Fri, 3 Jul 1998 22:45:39 +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 <11.C2DD249A@listserv.gmd.de>; Fri, 3 Jul 1998 22:45:37 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 378307 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 3 Jul 1998 22:45:32 +0200 Received: from kralle.zdv.Uni-Mainz.DE (kralle.zdv.Uni-Mainz.DE [134.93.8.158]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id WAA17398 for ; Fri, 3 Jul 1998 22:45:30 +0200 (MET DST) Received: (from Ufrank@localhost) by kralle.zdv.Uni-Mainz.DE (8.8.8/8.8.8) id WAA11641 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Fri, 3 Jul 1998 22:45:31 +0200 (MET DST) X-Authentication-Warning: kralle.zdv.Uni-Mainz.DE: Ufrank set sender to latex3 using -f Received: (from latex3@localhost) by frank.zdv.uni-mainz.de (8.6.9/8.6.9) id UAA00254; Fri, 3 Jul 1998 20:14:36 +0200 References: <199807021940.VAA01123@frank.zdv.uni-mainz.de> <9807030404.aa09947@boole.maths.tcd.ie> Message-ID: <199807031814.UAA00254@frank.zdv.uni-mainz.de> Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9807030404.aa09947@boole.maths.tcd.ie> Date: Fri, 3 Jul 1998 20:14:36 +0200 From: Frank Mittelbach Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: First experience with xr under L3PL Status: R X-Status: X-Keywords: X-UID: 2648 Tim, > However, I am still puzzled by the purpose of it all. > The new xr.sty is manifestly more difficult to follow > than its predecessor. is it really are are you only slightly taken aback by the many _ which is used to typical latex code with @ signs is something one needs to use two or three times to get used to. if this is a problem for you try looking at it using a global replace with _ to @ the example chosen by Richerd in the first place is perhaps not that good as it is not allowing you to really make use of the features of the language. the only think i used was the \seq module (sorry:-) which actually also implements stacks so i could push and pop aux file names onto the variable \l_xr_subfiles_seq and a few of these test commands like \ior_eof:NTF which made the code a lot more compact. in fact just by concerting it i found that i could do the package with a much simpler algorithm at it is implemented right now. > So who is meant to benefit ? > The user, the package writer, ... ? the package writer in the first place, the user indirectly as it should lead to cleaner internal code which works better together. > And what exactly is the benefit ? as the example chosen does not really contain much code there is not much benefit (other than those i tried to explain), for example all the benefit about argument handling is not used. but who knows, perhaps Richard (when the Europeans are sleeping) is trying it once more on a more complex example (hopefully really trying to use the additional functionality offered as well) maybe there are others who wish to comment on the different versions? frank