MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <AFA791BD-820C-4762-AF99-680B5A3DFA07@gmail.com>
            <4936E30A.5080209@morningstar2.co.uk>
            <87ljuxlybp.fsf@fawkes.hogwarts>
            <49370743.7050004@morningstar2.co.uk>
            <18745.37877.845526.230207@morse.mittelbach-online.de>
            <A9325DBA-A80E-4A6B-BE2B-B9FA4F005902@gmail.com>
            <18747.60665.106015.681211@morse.mittelbach-online.de>
            <944107A6-E45B-4F33-8F7B-AF98DC95AB54@gmail.com>
Message-ID:  <18748.52807.627728.138832@morse.mittelbach-online.de>
Date:         Mon, 8 Dec 2008 08:35:35 +0100
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: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: expl3 "token list" terminology
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <944107A6-E45B-4F33-8F7B-AF98DC95AB54@gmail.com>
Precedence: list
Status: R

Will Robertson writes:
 > On 08/12/2008, at 2:04 AM, Frank Mittelbach wrote:
 > >
 > > well you got me thinking on that level, because tlp could be named  
 > > tlist to
 > > fit with plist clist.
 > >
 > > the problem seems to be more in the later addition of the \tlist  
 > > functions
 > > that in contrast to anything else do not operate on some storage  
 > > bins but on
 > > tokens in the input stream.
 > 
 > Hmmm, I agree tlist would be nice and consistent; after all we don't  
 > have "clist pointers" and "plist pointers". But then what would we  
 > rename what are currently tlists?

that's the problem. It is something like \tlstream or \tstream (operating on
an input stream of token (list)), but I'm not sure this makes it better (only
longer)

Another point to consider is that _tlp is the predominant storage bin used
all over the place, so something snappy might be preferable over something
longer (such as _tlist)

frank