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 o8LMAmwx018319 for ; Wed, 22 Sep 2010 00:10:49 +0200 Received: (qmail 11478 invoked by alias); 21 Sep 2010 22:10:43 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 21 Sep 2010 22:10:43 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx105) with SMTP; 22 Sep 2010 00:10:43 +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 o8LM8lXr013722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Sep 2010 00:08:48 +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 o8LM147l010542; Wed, 22 Sep 2010 00:08:44 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 434505 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 22 Sep 2010 00:08:44 +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 o8LM8i7e011963 for ; Wed, 22 Sep 2010 00:08:44 +0200 Received: from oberon.open.ac.uk (oberon.open.ac.uk [137.108.141.46]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id o8LM8T1i013456 for ; Wed, 22 Sep 2010 00:08:32 +0200 X-IronPort-AV: E=Sophos;i="4.56,402,1280703600"; d="scan'208";a="53434346" X-Disclaimed: 1 Importance: Normal X-Priority: 3 (Normal) References: <4C967C9B.5010706@gmx.de> <71ED7A5B-DE11-45D9-9785-95A1DC795080@gmail.com> <4C9724B4.3010301@residenset.net> <19607.26705.947540.499705@morse.mittelbach-online.de> <4C9840AB.4050805@gmx.de> <732A7500-5414-4818-87E3-33CB14463288@gmail.com>, <4C98435A.1050507@gmx.de> MIME-Version: 1.0 X-Mailer: Lotus Domino Web Server Release 8.5.2 HF16 August 30, 2010 X-MIMETrack: Serialize by HTTP Server on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 21/09/2010 23:08:33, Serialize complete at 21/09/2010 23:08:33, Itemize by HTTP Server on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 21/09/2010 23:08:33, Serialize by Router on mcs-notes1/mcs/UK(Release 8.5.2 HF16|August 30, 2010) at 21/09/2010 23:08:33 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id o8LM8i7e011964 Message-ID: Date: Tue, 21 Sep 2010 23:08:33 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Chris Rowley Subject: Re: boolean expressions in ExplSyntaxNames To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4C98435A.1050507@gmx.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p77e5KAPs1l6v/Sb97LojnDtMgfETrECMLUO9erHzOJe+OynZRhvlGqb5A0X bbiCt2rAnnct/NAlbHMvoAL6GY+23tB3khNK7YMk+ONqcQ8h4HHJoBtGOmrvNj+HJMmLLset8EwG 6ybhA==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: 6435 My experience of dealing with language design for 'operators that get extended from binary (infix) to what computing people call 'nary' or 'n-ary' (NOT the meaning I used for this as a mathematician) is that it is best to define a distinct operator that acts on a sequence (or list if you want potential unboundedness). I am unsure whether it is relevant here to point out that this idea has a long mathematical pedigree in the use of 'summation-sigma' for repeated addition over a finite but arbitrary sequence. This would give Arno's: or possibly something more explitly a sequence/list inside. \bool_and_p:n {\bool1,...,\booln} But I would never wish to deprive others of complex infix operator expressions (even non-associative and non-commutative ones if they insist) After all, we inflict them on our kids from the very beginning. Who knows, our gene pool may be specially adapted to make us love them:-). chris -----Arno Trautmann wrote: ----- To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE From: Arno Trautmann Date: 21/09/2010 06:32 Subject: Re: boolean expressions in ExplSyntaxNames Will Robertson wrote: > On 21/09/2010, at 2:50 PM, Arno Trautmann wrote: > >> Will Robertson wrote: >>> On 20/09/2010, at 11:27 PM, Frank Mittelbach wrote: >>> >>>> is there actually any need for the :nnn etc versions? >>> >>> Not sure, is there? >>> They seem natural to me; better than nesting multiple :nn commands for more than two ‘and’ branches, say. >> >> But then you’re lost at five ”and“. What about, say >> \bool_and_p:n {\bool1,...,\booln} >> i.e. a list of boolean expressions? (Just for the interface, no idea how >> to implement this in an efficient way) > > Why not just use && in the first place? Because of possible catcode-troubles? ;) Or maybe such a list might be more useful for a xor operation. cheers Arno [attachment "signature.asc" removed by Chris Rowley/mcs/UK] --------------------------------------------------------------------------- The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302)