Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Sep 2008 14:42:55 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m8ACgkB5006294 for ; Wed, 10 Sep 2008 14:42:47 +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 m8ACbhPm031073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2008 14:37:43 +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 m89M1PEI032197; Wed, 10 Sep 2008 14:37:43 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 31681 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Sep 2008 14:37:43 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m8ACbgmv006025 for ; Wed, 10 Sep 2008 14:37:42 +0200 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.249]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id m8ACbbdP014963 for ; Wed, 10 Sep 2008 14:37:41 +0200 Received: by rv-out-0708.google.com with SMTP id c5so2199713rvf.10 for ; Wed, 10 Sep 2008 05:37:37 -0700 (PDT) Received: by 10.140.172.19 with SMTP id u19mr760120rve.31.1221050257201; Wed, 10 Sep 2008 05:37:37 -0700 (PDT) Received: from ?10.0.1.102? ( [219.90.231.17]) by mx.google.com with ESMTPS id g31sm12138801rvb.7.2008.09.10.05.37.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Sep 2008 05:37:36 -0700 (PDT) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) References: <48C3DAD1.6030004@morningstar2.co.uk> <4B6A6CEE-A06F-4EAC-B618-3B637A5902E4@gmail.com> <18630.50165.621679.420173@morse.mittelbach-online.de> <20B59161-A27F-4FE5-98E5-0FB3F051073B@gmail.com> <18631.42022.160484.847483@morse.mittelbach-online.de> X-Mailer: Apple Mail (2.928.1) X-Spam-Whitelist: Message-ID: <4077B37F-1E0A-4AD6-A450-7428D0912226@gmail.com> Date: Wed, 10 Sep 2008 22:07:31 +0930 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: expl3 variant expansion forms To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <18631.42022.160484.847483@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 10 Sep 2008 12:42:55.0440 (UTC) FILETIME=[BF435500:01C91342] Status: R X-Status: X-Keywords: X-UID: 5272 Hi Frank, On 10/09/2008, at 8:10 PM, Frank Mittelbach wrote: >> When I first read about expl3 years ago, indeed I was naively >> disappointed that the variants weren't constructed "on the fly". But >> that's obviously impossible. > > obviously impossible is perhaps too strong a word I do have a tendency to exaggerate :) > for example, while tlp and toks probably need access equally from > both sides > this is questionable for clists (imho). so just providing the base > function > rather than 10 variants on top for the _left case here isn't > something I would > feel too bad about. Leaving aside the further-reaching implications of switching to a push/ pop naming scheme exclusively (which I have no comment on right now), this issue of _left and _right functions being rather different in their usage patterns does concern me a little bit. For now I'll leave them "symmetrical" but this should be re-evaluated at the same time the push/pop/etc terminology is decided. >> So I was probably a little unclear about my intentions for that code. >> Does my reasoning make sense, in the end? > > my initial mail was not a reply to the specific proposal but about > the danger > of going overboard with providing all kind of variants Noted and agreed, thanks. Please do let me know when I'm overstepping the mark, however. I'll trim down what's currently there and re-document the unusual variants that have been added to expl3 for the one or two instances they're used in the xpackages. Best regards, Will