Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Sep 2008 22:26:29 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m8GKQONc000765 for ; Tue, 16 Sep 2008 22:26:25 +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 m8GKJ5si030644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Sep 2008 22:19: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 m8GElg5Z032032; Tue, 16 Sep 2008 22:18:55 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 44829 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 16 Sep 2008 22:18:55 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m8GKIsek003058 for ; Tue, 16 Sep 2008 22:18:54 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id m8GKIpGg020413 for ; Tue, 16 Sep 2008 22:18:54 +0200 Received: from morse.mittelbach-online.de (p4FD44A47.dip.t-dialin.net [79.212.74.71]) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis) id 0ML25U-1Kfh0c3Y20-00069o; Tue, 16 Sep 2008 22:18:51 +0200 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id BBC15654F5; Tue, 16 Sep 2008 22:18:47 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <48CCBAEE.60703@morningstar2.co.uk> <97AFAC39-1BDF-4EEB-8498-011976315F19@gmail.com> <36A84A57-FB7C-4729-AA03-5DBB74246850@gmail.com> <48CF4A7C.3080802@morningstar2.co.uk> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX19sxXGW3KxpC5DKaowKr6GejfETwluZ2ZrqYMJ NdfMbRhLfbpvxl1lDuoJNcJ6oyo6QiR2xDULPrP1SosWYckslv aQCTyilodDkBMCl+hds2I5vjDFp8nnX X-Spam-Whitelist-Provider: Message-ID: <18640.5287.478184.826238@morse.mittelbach-online.de> Date: Tue, 16 Sep 2008 22:18:47 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: Generic quark test To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <48CF4A7C.3080802@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -102.464 () BAYES_00,FORGED_RCVD_HELO,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 16 Sep 2008 20:26:29.0680 (UTC) FILETIME=[80520B00:01C9183A] Status: R X-Status: X-Keywords: X-UID: 5330 Joseph Wright writes: > Will Robertson wrote: > > Hi, > > > > I've been thinking more about this. > > Just so we're clear, what you're looking for is a function that can be > > given a token list and return true or false depending if, without > > expansion, the list contains a quark. > > I was thinking on a much less grand scale. Currently, you can test if > tlp contains a quark (usually q_no_value). However, the moment you > create a second quark to indicate something else (lets say > q_value_required) you always need two tests. If you have more > possibilities, the number of tests rises. Of course, you are probably > using these quarks separately, but in some places you may need a simple > "Is it a quark? yes/no" test. well, first of all, quarks are really made to be extremely fast in testing (though the need for this might vanish over time more and more) but essentially testing something for being one of three quarks isnt that bad. however, if you are really only interested in "is the token in #1 any quark" then you can do this (using the defining feature of a quark): \tlp_set:Nn\l_quark_test_tlp{#1} \if_meaning:NN \l_quark_test_tlp #1 ... assuming that #1 has picked up a token which may or may not be a quark is that what you are looking for? frank