Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 9 Sep 2008 17:58:44 +0200 Received: by mail.proteosys.com (8.13.8/8.13.8) with ESMTP id m89FwdNG007920 for ; Tue, 9 Sep 2008 17:58:39 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id m89FpZp8014339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Sep 2008 17:51:35 +0200 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m88M19mG015958; Tue, 9 Sep 2008 17:51:29 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 28272 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 9 Sep 2008 17:51:29 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id m89FpOgf002060 for ; Tue, 9 Sep 2008 17:51:29 +0200 Received: from spmler2.mail.eds.com (spmler2.mail.eds.com [194.128.225.188]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id m89Fp4PH011814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Tue, 9 Sep 2008 17:51:10 +0200 Received: from spmlir2.mail.eds.com (spmlir2-2.mail.eds.com [205.191.69.204]) by spmler2.mail.eds.com (8.14.2/8.13.8) with ESMTP id m89Fp3si021919 for ; Tue, 9 Sep 2008 16:51:03 +0100 Received: from spmlir2.mail.eds.com (localhost.localdomain [127.0.0.1]) by spmlir2.mail.eds.com (8.13.8/8.12.10) with ESMTP id m89FosCu017993 for ; Tue, 9 Sep 2008 16:50:54 +0100 Received: from defrm100.emea.corp.eds.com ([145.16.186.14]) by spmlir2.mail.eds.com (8.13.8/8.12.10) with ESMTP id m89ForGJ017983 for ; Tue, 9 Sep 2008 16:50:54 +0100 X-EDSINT-Source-Ip: 145.16.186.14 Received: from defrm202.emea.corp.eds.com ([145.16.186.18]) by defrm100.emea.corp.eds.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 9 Sep 2008 17:50:53 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: tlp type thread-index: AckSijTslw5w0srnQtaGoABBuazPuQAAINOQ References: A<48C68A0A.3030006@morningstar2.co.uk> X-OriginalArrivalTime: 09 Sep 2008 15:50:53.0611 (UTC) FILETIME=[D729E7B0:01C91293] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id m89FpTgf002080 Message-ID: <8D5403E89293A448A409DDDD1531CE1801951A44@defrm202.emea.corp.eds.com> Date: Tue, 9 Sep 2008 17:50:52 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "Mittelbach, Frank" Subject: AW: tlp type To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: A<48C68A0A.3030006@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -2.599 () BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE Status: R X-Status: X-Keywords: X-UID: 5255 Joseph, 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). another way to look at it is to think about whether "store_something" is used in a way of a variable or more in a way of a function call. I have had situations where I prefered to think of stored data as being stored in a function. For example in an interface for title page design, I had a bunch of functions (with arguments) and a bunch of functions without arguments (where where nothing else than storage bins really. But I treated them as functions because in the context of that interface it gave a uniform view rather than having some tings being variables and others being functions (with an argument) but essentially doing the same thing. so it depends I would say, but normally data bins should be variables of type _tlp 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 16:37 An: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE Betreff: tlp type Hello, A "philosophy" question. For storing values that will be used "as is", normally one would do \def\storesomething{Something}. In the LaTeX3 model, I can choose either \def:NNn \store_something: 0 {Something} or \tlp_new:N \l_store_something_tlp \tlp_set:Nn \l_store_something_tlp {Something} and get the same result, function-wise. Is the later closer to the model proposed, or should I stick with the former? -- Joseph Wright