Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Thread-Topic: AW: tlp type
thread-index: AckSmUMyVzRtvry/SuGiUf3PT8babAABjMew
Content-Transfer-Encoding: 8bit
Message-ID:  <8D5403E89293A448A409DDDD1531CE1801951A7D@defrm202.emea.corp.eds.com>
Date:         Tue, 9 Sep 2008 19:15:08 +0200
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: "Mittelbach, Frank" <frank.mittelbach@EDS.COM>
Subject: AW: AW: tlp type
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  A<48C6A3DE.4080508@morningstar2.co.uk>
Precedence: list
Status: R

you are absolutely right, which is why we intend to write up some introductory articles for TUB right now

frank 

-----Ursprüngliche Nachricht-----
Von: Mailing list for the LaTeX3 project [mailto:LATEX-L@LISTSERV.UNI-HEIDELBERG.DE] Im Auftrag von Joseph Wright
Gesendet: Dienstag, 9. September 2008 18:27
An: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Betreff: Re: AW: tlp type

Mittelbach, Frank wrote:

> philosophically tpls (token list pointers) have been invented precisely to be used to store data and not use "function definitions" for this (technically it uses \def:Npn of course, but it can for example do additional checks).

Good idea.  Perhaps the docs could mention this, to explain to existing (La)TeX coders that there is meant to clean separation between macros and storage (even though they both do the same thing "underneath).

A quick overview of the different storage types and their intended use might be handy.  You have to read quite a bit to even begin to get it (and so far I am obviously not quite there!).
--
Joseph Wright