Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Wed, 3 Dec 2008 14:13:38 +0100 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id mB3DDav5025461 for ; Wed, 3 Dec 2008 14:13:37 +0100 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 mB3D80s1002080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2008 14:08:00 +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 mB3BGI8g005073; Wed, 3 Dec 2008 14:07:14 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 176221 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 3 Dec 2008 14:07:14 +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 mB3D7ExV018414 for ; Wed, 3 Dec 2008 14:07:14 +0100 Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.243]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id mB3D7bog001686 for ; Wed, 3 Dec 2008 14:07:43 +0100 Received: by rv-out-0708.google.com with SMTP id c5so3486642rvf.10 for ; Wed, 03 Dec 2008 05:07:06 -0800 (PST) Received: by 10.140.193.16 with SMTP id q16mr6314983rvf.94.1228309626698; Wed, 03 Dec 2008 05:07:06 -0800 (PST) Received: from ?10.0.1.102? (219-90-188-36.ip.adam.com.au [219.90.188.36]) by mx.google.com with ESMTPS id b39sm5627566rvf.0.2008.12.03.05.07.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 03 Dec 2008 05:07:05 -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) X-Mailer: Apple Mail (2.929.2) X-Spam-Whitelist: Message-ID: Date: Wed, 3 Dec 2008 23:37:01 +1030 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Will Robertson Subject: expl3 "token list" terminology To: LATEX-L@LISTSERV.UNI-HEIDELBERG.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: 03 Dec 2008 13:13:38.0508 (UTC) FILETIME=[F48430C0:01C95548] Status: R X-Status: X-Keywords: X-UID: 5485 Hello, The expl3 modules defines data types for working with "lists of tokens". To summarise, a "token list pointer" is the name given to a control sequence that is a macro with some contents that takes no arguments. E.g., "\foo" is a tlp here: \def\foo{abc} By contrast, a "token register" is the name given to what I'd usually call a "toks", which has the property of being a little more lenient with the types of tokens it will accept as contents. The problem that I'm trying to solve is what to call the contents of these two distinct beasts. In the documentation in expl3, both toks and tlps are described to contain "token lists", but that's clearly not the best state of affairs. I think "token list" describes the contents of a toks rather well (as it should!) but I'm at a lost what to call "a token list that doesn't contain unescaped # characters". Would "character list" work? Will