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 p0QELj2N026021 for ; Wed, 26 Jan 2011 15:21:46 +0100 Received: (qmail 12946 invoked by alias); 26 Jan 2011 14:14:59 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 26 Jan 2011 14:14:59 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx018) with SMTP; 26 Jan 2011 15:14:59 +0100 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 p0QECsiF022085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 15:12:54 +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 p0QDVA6p001609; Wed, 26 Jan 2011 15:12:52 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 945216 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 26 Jan 2011 15:12:52 +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 p0QECqFp007299 for ; Wed, 26 Jan 2011 15:12:52 +0100 Received: from mail-yw0-f49.google.com (mail-yw0-f49.google.com [209.85.213.49]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p0QEClB1028397 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=FAIL) for ; Wed, 26 Jan 2011 15:12:51 +0100 Received: by ywf7 with SMTP id 7so204069ywf.22 for ; Wed, 26 Jan 2011 06:12:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.212.8 with SMTP id k8mr1227505ybg.60.1296051166989; Wed, 26 Jan 2011 06:12:46 -0800 (PST) Received: by 10.147.39.3 with HTTP; Wed, 26 Jan 2011 06:12:46 -0800 (PST) References: <3986.1295947424@cl.cam.ac.uk> Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Whitelist: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id p0QECqFp007300 Message-ID: Date: Wed, 26 Jan 2011 09:12:46 -0500 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Bruno Le Floch Subject: Re: \clist_length:N and \clist_nth:N 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 (Mail was not recognized as spam); Detail=5D7Q89H36p4WX0t+AtsdWzrXATe7U7iyEYsVEub6UEScnitTuLsF1TdlrkUKNRhypl1WP P4z9N2hLfJzsGszrlv+ygay/ivx19oyBwO3NEg0raNb/3tCvONPdaWhG3fyrhob4EvcA0r7m4G7q eqN5w==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: 6575 > I don't have any issue with element or elt (having been exposed to lisp long > time ago) but my feeling is that "length" is rather a good name for the > concept, but then we should use it in other places too and get rid of > elt_count there. > > For _nth I think _element is ok, but I'm not so sure why _item would be bad. > Don't see that there would be a conflict with other "items" of LaTeX. In > fact it is the same concept, so why choose different names? I agree with Frank: the "only" difference between clists and list-based environment is the separator: comma in one case, \item in the other. Bruno > Am 25.01.2011 um 10:37 schrieb "Robin Fairbairns" > : > >> Joseph Wright wrote: >> >>> On 24/01/2011 14:01, Lars Hellström wrote: >>>> Isn't this "elt" an implementation detail for that type of list (various >>>> \@elt tokens in 2e come to mind), and thus something that should be kept >>>> internal rather than canonised in a public interface? The clean solution >>>> for *both* types of list is rather to use "length". >>> >>> Seems reasonable: one would normally talk about 'a long list of things >>> to do', so lists to have 'length' :-) >> >> in some ways of looking at a list, it has 'length'. >> >> in plain english, i would say lists have "items" (or just "things") >> rather than "elements", but "item" is already heavily overloaded in >> the user's level latex-ese. i don't have a problem with "element" (or >> "elt" in command names). >> >>>> Moreover, I get a vague impression that the term `elt' is part of the >>>> pseudo-LISP heritage of LaTeX (emphasis on the "La"). If so, then that >>>> is IMHO another reason to avoid it, as that heritage is full of square >>>> pegs trying to fit in round holes. >>> >>> Not being familiar with Lisp, I can only go on things like LaTeX2e's >>> \@cdr, etc., which have much more sensible names in expl3. >> >> the "lisp heritage" is no more than simple use of some lisp names for >> some latex internal operations (e.g., car, cdr). it's a long time (>40 >> years) since i learned lisp, but i don't remember a special name for >> items in a lisp list. >> >>>>> I didn't write "clist_nth" with a view of it being the permanent name, >>>>> but >>>>> now that I've written it I can't think of a (good) alternative. Any >>>>> thoughts? >>>> >>>> I think the verb you're looking for is "index", i.e., the command name >>>> would be clist_index. >> >> hmm. index works, but i don't think it supports the "plain english" test. >> >>> I'd imagine 'index' to be the other way around: >>> >>> \clist_index:Nn \l_some_clist { item } => Number >> >> agreed. >> >>> whereas what Will has implemented gives the 'entry', 'element', 'item' >>> or some such name. ('element' seems to be discouraged based on the first >>> part of your e-mail, so perhaps 'item' is better.) >> >> i think element is as good as it gets, in this context. >> >>>> first: Return index of first occurrence of a particular item within a >>>> clist, >>>> or -1 (given 0-based indices) if the item does not occur therein. >>>> last: Return index of last occurrence of a particular item within a >>>> clist, >>>> or -1 (given 0-based indices) if the item does not occur therein. >>>> (Note: Slightly trickier to implement.) >>> >>> Both of these look relatively easy to do. >>> >>>> range: Return a subrange of the clist, i.e., if \a_clist is "a,b,c,d" >>>> then >>>> \clist_range:Nnn\a_clist{1}{2} returns "b,c". (I don't have an >>>> opinion as to what might be the best sense of "return" in this >>>> case.) >>>> replace: Replace the material in a subrange of the clist by some other >>>> clist material. >>> >>> More tricky. Let's sort the others first :-) >> >> robin >> >> getting better every day. very slightly. >