Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Sep 2008 13:14:19 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m8ABEE0x032100 for ; Wed, 10 Sep 2008 13:14:15 +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 m8AB9wsK000702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2008 13:09:59 +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 m89M1P5E032197; Wed, 10 Sep 2008 13:09:55 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 31081 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Sep 2008 13:09:55 +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 m8AB9tj2030273 for ; Wed, 10 Sep 2008 13:09:55 +0200 Received: from atlas.informatik.uni-freiburg.de (atlas.informatik.uni-freiburg.de [132.230.150.3]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m8AB9gBU000459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 10 Sep 2008 13:09:46 +0200 Received: from remote239-13.home.uni-freiburg.de ([132.230.239.13] helo=irwin.vpn.uni-freiburg.de) by atlas.informatik.uni-freiburg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1KdNZt-0000qw-2o for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Sep 2008 13:09:42 +0200 Received: by irwin.vpn.uni-freiburg.de (Postfix, from userid 500) id 5A58F1782E; Wed, 10 Sep 2008 13:07:25 +0200 (CEST) Mail-Followup-To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Message-ID: <20080910110725.GA3944@irwin.vpn.uni-freiburg.de> Date: Wed, 10 Sep 2008 13:07:25 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Heiko Oberdiek 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 11:14:20.0032 (UTC) FILETIME=[5F087000:01C91336] Status: R X-Status: X-Keywords: X-UID: 5269 Hello, On Wed, Sep 10, 2008 at 12:40:38PM +0200, 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, How do you want to define macros on the fly, being in expandable contexts (inside \edef, \write, ...)? Or is the use of these macros forbidden inside expandable contexts? Next question, how does the "on the fly" process (if such a thing might exist) decide to define a macro globally or locally? Local stuff making global isn't a good idea generally, thus local definitions remain. But this can be ineffective, if the yet undefined variant is only called inside a separate group. Yours sincerely Heiko