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: <AFA791BD-820C-4762-AF99-680B5A3DFA07@gmail.com>
            <4936887F.2080304@morningstar2.co.uk>
Message-ID:  <2927DDEB-1C99-40CC-A53F-41C7A92CC264@gmail.com>
Date:         Thu, 4 Dec 2008 10:06:17 +1030
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Will Robertson <wspr81@GMAIL.COM>
Subject: Re: expl3 "token list" terminology
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <4936887F.2080304@morningstar2.co.uk>
Precedence: list
Status: R

Hi Joseph & Andreas & others,

On 03/12/2008, at 11:54 PM, Joseph Wright wrote:

> I'd call it a string, but there we are. (Most other languages use the
> term "string" for stored text: token lists are a very TeX idea.)
> However, "character list" sounds okay to me.

I changed my mind, overnight -- to me, "character list" doesn't really  
convey the contents of a "token list" like
   {\ifx\tmpa\empty foo\else bar\fi}

I wasn't really thinking of changing the name of the module at this  
stage, I was just trying to clarify the documentation a little.

Perhaps it would be fine to continue to use "token list" for each and  
just explain in more detail what we mean by this at the beginning of  
l3tlp and l3toks.

* * *

Silly idea: call one "list of tokens" or even just "tokens" and the  
other "token list" :) But which would be which?

Will