LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0 (Apple Message framework v929.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Date: Thu, 4 Dec 2008 10:06:17 +1030
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Will Robertson <[log in to unmask]>
In-Reply-To: <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments: text/plain (26 lines)
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?