Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id s6FM6Age014141 for ; Wed, 16 Jul 2014 00:06:11 +0200 Received: from relay2.uni-heidelberg.de ([129.206.210.211]) by mx-ha.gmx.net (mxgmx105) with ESMTPS (Nemesis) id 0Meu6H-1WvzdN2zlJ-00OUAC for ; Wed, 16 Jul 2014 00:06: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 s6FM3HRl022707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Jul 2014 00:03:18 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s6FM14At017222; Wed, 16 Jul 2014 00:03:17 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 11178242 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 16 Jul 2014 00:03:17 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s6FM3Hu3017926 for ; Wed, 16 Jul 2014 00:03:17 +0200 Received: from smtp3.clear.net.nz (smtp3.clear.net.nz [203.97.33.64]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id s6FM34Wj022672 for ; Wed, 16 Jul 2014 00:03:08 +0200 Received: from mxin2-orange.clear.net.nz (lb2-srcnat.clear.net.nz [203.97.32.237]) by smtp3.clear.net.nz (CLEAR Net Mail) with ESMTP id <0N8R008Q8X6SYY40@smtp3.clear.net.nz> for LATEX-L@listserv.uni-heidelberg.de; Wed, 16 Jul 2014 10:03:03 +1200 (NZST) Received: from 121-74-37-59.telstraclear.net (HELO [127.0.0.1]) ([121.74.37.59]) by smtpin2.clear.net.nz with ESMTP; Wed, 16 Jul 2014 10:02:53 +1200 MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7bit X-Antivirus: avast! (VPS 140715-1, 16/07/2014), Outbound message X-Antivirus-Status: Clean References: <539432A6.7030205@clear.net.nz> <5395A7A3.7040106@residenset.net> <5395AA02.8040704@morningstar2.co.uk> <53BF8686.2060201@morningstar2.co.uk> <53C0131F.2030404@morningstar2.co.uk> <53C09731.6080004@clear.net.nz> <53C0BDC3.9010007@clear.net.nz> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 Message-ID: <53C5A50B.5040206@clear.net.nz> Date: Wed, 16 Jul 2014 10:02:51 +1200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: aparsloe Subject: Re: Juxtaposition in l3fp To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: Envelope-To: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=V3; X-GMX-Antivirus: 0 (no virus found) X-UI-Filterresults: notjunk:1;V01:K0:nm9QlR/OIVU=:D52PzJsm3A7D3T8wR5SEizLEBg SvURD1tDC7ruJk3WXwbOI2BCCDehi3CEW6XscJF+qoJcG2iK24LRhTxHpD87sWIJED+RYZHm9 QtfnomsUuYu2QnWsMv1lmBaOXZGxg27fPaTmstYBhRjDlXdH6BHzl++AXHsj0m2DWKgHyvRuD 7P3zQnhGIeGV9eLLpqeaJ9F7urtznmN0+kEj72bpGJazRNpXN9pSnFh1h2AXBdNhd10mo5vDS VDSuYnMVm6Wml8u+1GDFGc/Th9B/yrq6DOeEGie6R6OBn6LZ3IjnHrD6wMkga8+GYWOHPWzPl R4vTelG9lY5P8XCKDAvC5X8ckZ074YBOoU/MSrxcmE4r7H1gV75IcjI1nIyA1c5J/niBIM6Ll 43iOb+xqhd8oN02ExS3hApnRxAHb8AszPETGFIMgV1UAe5KIu5lRn2elaDEBwGsR8AyFz89u2 NdQNKlGyXb2P9LqlBl/2nZKNLPIcJ2xzV2U5iRn1iVYCTs92/0UbJdxMS7EgOjZplQy/VT+uz Psd6azf88vbhM/qe8/zY6l51HY3OkttLt1d5scLsXH/qtqDkA7+m+yLn6M8ULNmwC+OzA8KBt UP8GVNtgXCCViI7ZL9k5wGfGnOrfwQGvibVcGYv9p78nmNXL2wLhoTrM1Mln+Xk2wH68tZyfo LW6A9Uw+6CW5YIOOrPnHWbuUg8g/0YhcQwPgy9Nk5+Md2Tt5cyo01DU+Q6h3sB9e+czCFEyO8 lQ9pDwusUHSiD968tnMHksHQA/ezZsdNGe4xEF0vvfAtT9XphCWIw23CrT4e6QDuPAiKcqUVg c9a65trNEeurSJgBCGBOV3oJ6zgYczolUHVyoLFsUgq2eEJqRxU+mqGtek6N9Bp+IZJdwc3lJ zjaR2MkAWqOah7+ibTZ+9h3Rcb0ML0cK864zM4xTJdL8sXsWcVdUuzRPLByLYroKQ9f5wqLHx Rnld4ZxgEls585qwCHyUQoB6WbulHKcRgTs8LdOtGraCem/A68h4gXsDGJtSLvsLhT48+VtO9 +GWED6eBnyhQrrnHx18E0WiRQ7euGpCWF7NY2hHSZClXYOCjzWCHK7wTSu6xVT02A6Ywxxhxb TtmdG/5QbQZxcxksrJ1EA9A6Q6RwIKstpxWAZKgyEMnnhlPdRZ6FdtlpuQXwHVFciWRBqKWYi PoZPWAtZwTHzGQPkYu/Dk+1UwBh3m73gyVw5L2vc8lRLwpRmukRBIdVwC4OAnsAOJFwtH3qLV KkRYUS7sVJjiJm4E5yYqA2y5j/IZSdsIZDr8geH3XvqJIgz+wYBtq4TUzQFzfvGGUyrHK0Sf0 tAKWUZPLvnZ/c/EsAfjIohKXydr1vyKp1bfIiWGBfo+nSFd54utdtlRrjS9VRWXQDq/8tjegj NjONAVi9B7mSYSjQjUPB+xG+JIh1EAbLwp0EY479M93U+3k+D+lHL2btQ6OP86Y77MvI77iq3 H+BqaA1RcLhswr+ZOZqEU3dPnjIFShxzI2YOeYzctXk5XgatSOoaABryR5L5R/6lLaRryS0g= = X-UI-Loop:V01:Ka2BnwFMguk=:lbLPP92J369+PoX5pWzTYi70ZL5swKk0/ZpeBcB9elM= Status: R X-Status: X-Keywords: X-UID: 7552 On 16/07/2014 2:00 a.m., Bruno Le Floch wrote: > On 7/12/14, aparsloe wrote: >> On 12/07/2014 3:13 p.m., Bruno Le Floch wrote: >>> Can you expand on that one exception? I don't see what it is. >> I found myself on occasion wanting to substitute a number in expressions >> where pi is followed by other terms. For instance the fine structure >> constant is 2pi e^2/hc (where e is the electronic charge in this case) >> but direct substitution of values for e etc. simply provokes an >> "Undefined control sequence" message. Since numbers are not (as far as I >> understand) elements of control sequences, this felt like an unnecessary >> limitation. (But I'm not familiar with the underlying constraints. Hence >> the "perhaps".) > Not sure what you mean here. Doing \fp_show:n { 2pi e^2/hc } gives two errors: > > \LaTeX3 error: Unknown fp word pie. > \LaTeX3 error: Unknown fp word hc. > > Doing > > \fp_const:Nn \c_aparsloe_e_fp { 1.60217657e-19 } > \fp_const:Nn \c_aparsloe_h_fp { 6.62606957e-34 } > \fp_const:Nn \c_aparsloe_c_fp { 299 792 458 } > \fp_show:n { 2pi \c_aparsloe_e_fp ^2 / ( \c_aparsloe_h_fp > \c_aparsloe_c_fp ) } > > works (except that since I've used values in SI units for e, h, c, the > formula for the fine structure constant is missing a factor of > sqrt(4pi*epsilon0)). > >> As I've tried to indicate, I've come to realise that what matters is >> clarity in what the rules are and the rigour of their application. My >> concern was with people who might, at present, use a (clunky?) package >> like calc, or fp, coming across l3fp, being seduced (like me) and coming >> a cropper (as I did). The proposed change will certainly reduce that >> possibility. > I'm not sure what change you propose (besides the precedence of > juxtaposition, which will change soonish), and it will be helpful if > you clarify. > > Regards, > Bruno OK, my example, has misled. I simply wondered why pi2 (for instance) is not acceptable to l3fp? And in the same vein, why is (3)2 not accepted, whereas (3)(2) and 3(2) are accepted? This rejection by l3fp of "trailing numbers" felt to me like an oversight in the otherwise rigorous application of juxtaposition. Andrew