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 pB4Lk1Dw005699 for ; Sun, 4 Dec 2011 22:46:02 +0100 Received: (qmail 27742 invoked by alias); 4 Dec 2011 21:45:56 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 04 Dec 2011 21:45:54 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx053) with SMTP; 04 Dec 2011 22:45:54 +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 pB4LhN7l026166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Dec 2011 22:43:24 +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 pB3N168k010506; Sun, 4 Dec 2011 22:43:23 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1927612 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 4 Dec 2011 22:43:23 +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 pB4LhN5o018878 for ; Sun, 4 Dec 2011 22:43:23 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id pB4LhC1j026133 for ; Sun, 4 Dec 2011 22:43:16 +0100 Received: from mittelbach-online.de (p3EE3F337.dip.t-dialin.net [62.227.243.55]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0Lg6Fn-1QzKn52UcV-00pgcN; Sun, 04 Dec 2011 22:43:12 +0100 Received: by mittelbach-online.de (Postfix, from userid 783) id A3B1E2202B2; Sun, 4 Dec 2011 22:43:07 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on Marlowe X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.2.5 Received: from [127.0.0.1] (unknown [192.168.123.100]) (Authenticated sender: frank) by mittelbach-online.de (Postfix) with ESMTPSA id 78DF82202AF for ; Sun, 4 Dec 2011 22:43:06 +0100 (CET) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 References: <4ED9ED20.40004@morningstar2.co.uk> <4EDA0732.5060003@latex-project.org> <4EDB8079.6000707@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 111204-1, 04.12.2011), Outbound message X-Antivirus-Status: Clean X-Provags-ID: V02:K0:3YKLXESE5u9nokz9lFDiM+sk004r+e/okh1jfluY1TM fEobWmlw1PLGJ+ArodzOzj0d3DBWUUOi8f1VBEZfKsjH46sbED 84EjB9/zCQaOW2s+byZ6sQKnCbVcN+iI8c+wWhMDGEAmvgxMjL NL6lxLuIA9fLkyrbAGxjdYjliaptLENDuRscb0fyYQU/v8ew4Y EfSWh+Ni4aoCHJuAIzuoz/ssPVLl6f3skJ0jYpv5pItmx3ury0 hd4Fg1LchPQprR1e2+xHGx/k2bu48oZL16yTnYKbLYerH8JCTO uuCcmWT/qC2l8pNNompmP8Awx6mAI2uhjb2OuMala3hpQLy9xn cWyT1DeC68lAsRqj0ap4NM7iS037byeD0+RmuJ+vl Message-ID: <4EDBE96A.10806@latex-project.org> Date: Sun, 4 Dec 2011 22:43:06 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: Documentation of local/global variants To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p42lhgaIAOef8vfEUQBIZIw+ALjf+5ksOAwNKzbVlSaubZhnC9WpptWFUnV3 rwRRn6p+Q8Pr3a7lzC/Lw24c1XPZm8bICt9ZH6UgkxctVWgwrmJQEn3BSeitS0KxGrNFNM87O/2B 3H+S72ohAaa+py/nbxro1v4xLQsdnqPQyNQFIy6PP7FWQnBGGeYx7HdBN8=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: 6972 Am 04.12.2011 21:16, schrieb Bruno Le Floch: >> Yes, there are a few cases where such a convention would not be >> sufficient, for example \prop_(g)get:NnN. As I said, this mirrors the >> situation with TF functions, where there are a few in which the >> documentation does have to cover more complex situations on a >> case-by-case basis. > > Side note: \prop_gget:NnN doesn't and shouldn't exist. We may want to > add somewhere a mention that 'pop' and 'gpop' functions always return > their value locally. agreed, we decided long ago that all "get" or "pop" would be local in their return value and only in case of "pop" the change to the underlying data structure could be global. So yes that should probably better documented up front as well. > = > Where functions for variable manipulation can [perform assignments] > either locally or > globally, the latter case is indicated by the inclusion of a "g" in the > [second part] of the function name. Thus \tl_set:Nn is a local function but > \tl_gset:Nn acts globally. Functions of this type are always documented > together, and the scope of action may therefore be inferred from the > presence or absence of a "g". sounds good to me cheers frank