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 q78LZIxn009821 for ; Wed, 8 Aug 2012 23:35:19 +0200 Received: (qmail 22159 invoked by alias); 8 Aug 2012 21:35:13 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 08 Aug 2012 21:35:13 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx064) with SMTP; 08 Aug 2012 23:35:13 +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 q78LXAe9013970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Aug 2012 23:33:11 +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.1) with ESMTP id q78L1qJn008220; Wed, 8 Aug 2012 23:33:11 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 2611536 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 8 Aug 2012 23:33:11 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.8/8.13.1) with ESMTP id q78LXBB8008253 for ; Wed, 8 Aug 2012 23:33:11 +0200 Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q78LX6lE013941 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=FAIL) for ; Wed, 8 Aug 2012 23:33:09 +0200 Received: by vcbfl13 with SMTP id fl13so1624373vcb.22 for ; Wed, 08 Aug 2012 14:33:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.69.38 with SMTP id b6mr13142313vdu.22.1344461586361; Wed, 08 Aug 2012 14:33:06 -0700 (PDT) Received: by 10.58.124.136 with HTTP; Wed, 8 Aug 2012 14:33:06 -0700 (PDT) Content-Type: text/plain; charset=UTF-8 X-Spam-Whitelist: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id q78LXBB8008254 Message-ID: Date: Wed, 8 Aug 2012 17:33:06 -0400 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "Joel C. Salomon" Subject: Referring to a family of function variants To: LATEX-L@listserv.uni-heidelberg.de Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (BackTrace mail analyze); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnGL2vqOgpaBYL16oitsMrgDt/NQNpSCZFFjDOy 97xb7Zpf+wZnd5ZXNcvLDXR3Wg3wRjdQbwEMh8=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: 7111 Hi again. Is there some preferred style for referring to a family of function variants? For example, from xpeek: % \begin{macro}[aux]{\@@_if_in:NNTF} % \begin{arguments} % \item Token-list to search through (the “haystack”) % \item Token to search for (the “needle”) % \end{arguments} % Among the \cs{tl_if_in:**\textit{TF}} conditionals % defined in \pkg{expl3}, \cs{tl_if_in:NNTF} is missing. % But since that’s the functionality I need, define it: % \begin{macrocode} Is “\tl_if_in:**TF” (with or without “TF” being italicized) a recognizable, non-ambiguous way to refer to those functions as a set, or is there a nomenclature already in use that I should rather adopt? —Joel