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 p8ID09F8032109 for ; Sun, 18 Sep 2011 15:00:10 +0200 Received: (qmail 7526 invoked by alias); 18 Sep 2011 13:00:04 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 18 Sep 2011 13:00:04 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx022) with SMTP; 18 Sep 2011 15:00:04 +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 p8ICw1EV008418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Sep 2011 14:58:01 +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 p8HM14ZV032401; Sun, 18 Sep 2011 14:58:00 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1594308 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 18 Sep 2011 14:58:00 +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 p8ICw0PK012333 for ; Sun, 18 Sep 2011 14:58:00 +0200 Received: from ix.urz.uni-heidelberg.de (cyrus-portal.urz.uni-heidelberg.de [129.206.100.176]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p8ICvx7S015661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 18 Sep 2011 14:57:59 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p8ICvxkQ029671 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 18 Sep 2011 14:57:59 +0200 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id p8ICvmLM015248 for ; Sun, 18 Sep 2011 14:57:53 +0200 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R5GwK-0005eJ-BZ for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 18 Sep 2011 14:57:44 +0200 Received: from p5dd1c350.dip.t-dialin.net ([93.209.195.80]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Sep 2011 14:57:44 +0200 Received: from news3 by p5dd1c350.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Sep 2011 14:57:44 +0200 X-Injected-Via-Gmane: http://gmane.org/ Lines: 22 References: <4E6D0C75.6090500@morningstar2.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p5dd1c350.dip.t-dialin.net User-Agent: 40tude_Dialog/2.0.15.41de X-Spam-Flag: No X-Envelope-From: X-Spam-Status: No, hits=-4.40 required=5 tests=AWL,BAYES_00,L_P0F_Linux,RCVD_IN_DNSWL_MED,SPF_HELO_PASS, SPF_PASS Message-ID: <13xqgkr6dq2cr.dlg@nililand.de> Date: Sun, 18 Sep 2011 14:57:28 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Ulrike Fischer Subject: Re: Scratch variables To: LATEX-L@listserv.uni-heidelberg.de Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p5x1RWm4Ldx8pHNe5ytInNcugr1vdQuJXlvzrT+p0TkzJLKISKKiKCARv39p NeBg5yaibLIulbsrXVxXJdNgfY0LiSQtuQlq6FFot7Y5RPJVm126oXQXM/XI65H/KPVtjihej/3P YJloiKb2eSgqKiq36JG668Q3Ud2PA3V/gdKUKuovRhjx1Z4A1LIbEpbvSA=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: 6872 Am Sun, 11 Sep 2011 20:31:01 +0100 schrieb Joseph Wright: > Hello all, > > Currently, provision of scratch variables (such as \l_tmpa_tl) is > somewhat inconsistent in expl3. However, it is also not entirely clear > if these 'general scratch' variables are really idea in any case. Do > people see a general need for these variables, or will most users expect > to define their own scratch space in all cases? Well on the one side I still feel the urge to avoid to waste ressources. But on the other side at soon as user input is involved it can get difficult to be sure that code from other packages don't meddle with the scratch variables. So actually I use them only seldom. The only scratch "variable" which I think is really useful is a scratch read/write ressource. -- Ulrike Fischer