Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 11 Aug 2009 23:58:53 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n7BLwnbZ031445 for ; Tue, 11 Aug 2009 23:58:49 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n7BLs4iC009855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Aug 2009 23:54:05 +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 n7BJ3J61028140; Tue, 11 Aug 2009 23:54:04 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 295981 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 11 Aug 2009 23:54:03 +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 n7BLs3cX015664 for ; Tue, 11 Aug 2009 23:54:03 +0200 Received: from av9-1-sn2.hy.skanova.net (av9-1-sn2.hy.skanova.net [81.228.8.179]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n7BLro7P019223 for ; Tue, 11 Aug 2009 23:53:54 +0200 Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502) id D5ED4380AF; Tue, 11 Aug 2009 23:34:02 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id B92CD37E50 for ; Tue, 11 Aug 2009 23:34:02 +0200 (CEST) Received: from Kuben.local (90-230-192-94-no86.tbcn.telia.com [90.230.192.94]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 9B7B537E45 for ; Tue, 11 Aug 2009 23:34:02 +0200 (CEST) User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 References: <4A7921CF.5020803@morningstar2.co.uk> <4A7A1505.4040604@residenset.net> <4A7AD930.2090106@residenset.net> <8516B615-51AA-4D90-BB7D-A9E122AA0335@gmail.com> <4A816C31.9080401@residenset.net> <4A817463.8000805@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id n7BLs3cX015665 Message-ID: <4A81E3CA.6050608@residenset.net> Date: Tue, 11 Aug 2009 23:34:02 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: =?ISO-8859-1?Q?Lars_Hellstr=F6m?= Subject: Re: xparse To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <4A817463.8000805@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 11 Aug 2009 21:58:53.0151 (UTC) FILETIME=[EA6456F0:01CA1ACE] Status: R X-Status: X-Keywords: X-UID: 5894 Joseph Wright skrev: > Lars Hellström wrote: >>> } >>> \cs_generate_variant:Nn \foo_internal:n {V} >> I thought O was the appropriate variant for expanding a token list >> control sequence? > > The re-factor saw us drop "O", and sort-of downgrade "o" (we use it > less). The V specifier lets you write both > > \foo_internal:V \l_my_tl % A macro at the TeX level > > and > > \foo_internal:V \l_my_toks % A toks at the TeX level (o.0) Does it inspect the argument at runtime to figure out which of the two cases is at hand? Looks rather fragile & syntactic sugar to me. > whereas \foo_internal:o would need > > \foo_internal:o {\l_my_tl} > \foo_internal:o { \toks_use:N \l_my_toks } I think I would rather prefer that, myself! > So V is preferred for accessing variables (as the internal structure is > not important), Wouldn't you still need to know the variable's "internal structure" when setting it? Lars Hellström