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
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Wed, 3 Dec 2008 13:24:15 +0000
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (31 lines)
Will Robertson wrote:
> 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

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.
Joseph Wright