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 p078s5Kg001768 for ; Fri, 7 Jan 2011 09:54:06 +0100 Received: (qmail 28229 invoked by alias); 7 Jan 2011 08:54:00 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 07 Jan 2011 08:54:00 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx096) with SMTP; 07 Jan 2011 09:54:00 +0100 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 p078lI6w010107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jan 2011 09:47:19 +0100 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 p0776ebo013383; Fri, 7 Jan 2011 09:47:16 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 772604 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Fri, 7 Jan 2011 09:47:16 +0100 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 p078lGSm028052 for ; Fri, 7 Jan 2011 09:47:16 +0100 Received: from ueamailgate02.uea.ac.uk (ueamailgate02.uea.ac.uk [139.222.131.185]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p078l2In009966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 7 Jan 2011 09:47:06 +0100 Received: from ueams02.uea.ac.uk (ueams02.uea.ac.uk [139.222.131.131]) by ueamailgate02.uea.ac.uk (8.13.8/8.13.8) with ESMTP id p078l2tr027202; Fri, 7 Jan 2011 08:47:02 GMT Received: from [139.222.113.126] by ueams02.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1Pb7yO-0007vX-Eg; Fri, 07 Jan 2011 08:47:00 +0000 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 References: <4D20D031.7040803@gmx.de> <4D20DAE9.3070306@morningstar2.co.uk> <4D21D4CA.70703@morningstar2.co.uk> <2F1A4A24-7C35-4C2A-8E80-115DCD9510DF@YAHOO.DE> <4D21F6CE.10504@morningstar2.co.uk> <19748.63170.237158.614517@morse.mittelbach-online.de> <4D257ADD.5030101@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, outgoing) X-CanIt-Geo: ip=139.222.131.131; country=GB; region=I9; city=Norwich; latitude=52.6333; longitude=1.3000; http://maps.google.com/maps?q=52.6333,1.3000&z=6 X-CanItPRO-Stream: UEA:outgoing (inherits from UEA:default,base:default) X-Canit-Stats-ID: 66635511 - 8497fa4ea6b6 - 20110107 X-Scanned-By: CanIt (www . roaringpenguin . com) on 139.222.131.185 Message-ID: <4D26D308.5050904@morningstar2.co.uk> Date: Fri, 7 Jan 2011 08:47:04 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: \int_eval:n versus \dim_eval:n/skip_eval:n [was Re: l3luatex module] To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4D257ADD.5030101@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p77e5KAPs1l6v/Sb97LojnDtMgfETrECMLUO9erHzOJe+OynZRhvlGqb5A0X bbiCt2rAnnct/NAlbHMvoAL6GY+23tB3khNK7bnSLVW+CwI5D12EFi8O0kjG6WQoWUyJZa/tsAeZ e++4A==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: 6547 On 06/01/2011 08:18, Joseph Wright wrote: > I've gone back and forward through this, and I think in the end this is > the best plan. In the end, expl3 should be designed 'on its own merits', > and that may mean that some mixed plain TeX\expl3 cases are a little > awkward. For what we want, an expandable \int_eval:n makes most sense, > and by logical extension \dim_eval:n and \skip_eval:n should also be > expandable. > > What we do need to do is to make sure that this is clear in the > documentation, as Philipp has pointed out. Something like > > After two expansions, \int_eval:n yields a not an > . As a a result, it will require suitable > termination if used in a \TeX-style integer assignment. > > and a similar statement for dim and skip cases. This is now done in the SVN: I'll send it to CTAN in a few days. -- Joseph Wright