Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sat, 6 Dec 2008 03:43:12 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id mB62hAFL007841 for ; Sat, 6 Dec 2008 03:43:11 +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 mB62dIOp005498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Dec 2008 03:39:18 +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 mB5N1AXh021973; Sat, 6 Dec 2008 03:39:06 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 167558 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 6 Dec 2008 03:39:05 +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 mB62d5Fe005570 for ; Sat, 6 Dec 2008 03:39:05 +0100 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.250]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id mB62d0A3013667 for ; Sat, 6 Dec 2008 03:39:03 +0100 Received: by rv-out-0708.google.com with SMTP id c5so274329rvf.10 for ; Fri, 05 Dec 2008 18:39:00 -0800 (PST) Received: by 10.140.208.17 with SMTP id f17mr312702rvg.261.1228531140094; Fri, 05 Dec 2008 18:39:00 -0800 (PST) Received: from ?10.0.1.102? (219-90-176-178.ip.adam.com.au [219.90.176.178]) by mx.google.com with ESMTPS id b39sm9409424rvf.0.2008.12.05.18.38.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 05 Dec 2008 18:38:59 -0800 (PST) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) References: <4936E30A.5080209@morningstar2.co.uk> <87ljuxlybp.fsf@fawkes.hogwarts> <49370743.7050004@morningstar2.co.uk> <18745.37877.845526.230207@morse.mittelbach-online.de> X-Mailer: Apple Mail (2.929.2) X-Spam-Whitelist: Message-ID: Date: Sat, 6 Dec 2008 13:08:55 +1030 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: Re: expl3 "token list" terminology To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <18745.37877.845526.230207@morse.mittelbach-online.de> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 06 Dec 2008 02:43:12.0880 (UTC) FILETIME=[61ECA700:01C9574C] Status: R X-Status: X-Keywords: X-UID: 5514 On 06/12/2008, at 7:19 AM, Frank Mittelbach wrote: > I'm coming somewhat late to this discussion, but ... > > TeX (and as such expl3) deals with tokens and the replacement text > of a macro > without arguments is a list of tokens and not a list of characters > or a string > or... > > the contents of a toks register too is a list of tokens > > they are not the same in the way they can be accessed or manipulated > but their > content is the same. The more this is discussed the more I think that toks and tlp are fine names, and I wasn't thinking about changing them when I brought this up. I was just wondering if there was a short way to distinguish between what sort of material a toks and a tlp can contain. (I must have worded this particularly poorly.) So in the documentation when we write \toks_set:Nn {} cf. \tlp_set:Nn {} there might be some way of distinguishing the token list in the former compared to the latter. * * * I'm still thinking there's nothing we can do but refer to the contents of both as "token lists" and just mention the differences at the beginning of l3tlp and l3toks. Will