Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Sun, 16 Sep 2007 21:51:33 +0200 Received: by mail.proteosys.com (8.13.8/8.13.4) with ESMTP id l8GJpNKR028214 for ; Sun, 16 Sep 2007 21:51:24 +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 l8GJknkn024715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Sep 2007 21:46:50 +0200 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id l8FM1Nsn007395; Sun, 16 Sep 2007 21:46:42 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.0) with spool id 116352 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 16 Sep 2007 21:46:42 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id l8GJkg6j012029 for ; Sun, 16 Sep 2007 21:46:42 +0200 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id l8GJkev5024634 for ; Sun, 16 Sep 2007 21:46:44 +0200 Received: from p54A99358.dip0.t-ipconnect.de [84.169.147.88] (helo=morse.mittelbach-online.de) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1IX04i3vyk-00085o; Sun, 16 Sep 2007 21:46:37 +0200 Received: by morse.mittelbach-online.de (Postfix, from userid 501) id 4A359131B0; Sun, 16 Sep 2007 21:46:36 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <87abrn26y6.fsf@buckbeak.hogwarts> <18156.17180.930651.165216@morse.mittelbach-online.de> <87tzpucyxr.fsf@buckbeak.hogwarts> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Provags-ID: V01U2FsdGVkX1/h2R0UuswhfebwN2/1hUMX+5waqmC46JRPvHf +tvaN0fboG9Z3DyD/Hh9E9Q4ipE+3S6Eb3GXkXGwcyh/NbgrhA c8RcCThNR6i7/KKxAXknDJgYHIKuGvM X-Spam-Whitelist-Provider: Message-ID: <18157.34844.164457.783897@morse.mittelbach-online.de> Date: Sun, 16 Sep 2007 21:46:36 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: \tlp_use:N considered harmful? To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <87tzpucyxr.fsf@buckbeak.hogwarts> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -102.464 () BAYES_00,FORGED_RCVD_HELO,USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.57 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 16 Sep 2007 19:51:33.0989 (UTC) FILETIME=[FC007950:01C7F89A] Status: R X-Status: X-Keywords: X-UID: 5067 Andreas, small addendum > > > > And then: What's the error message in \tlp_use:N for? It looks > > > so arbitrarily. Probably it's not? > > > > well I don't know when that was added, but i can see some logic behind it (not > > that i think it is worth having really (as i think one should get rid of the > > whole cmd). I think the idea was that a tlp is a storage bin so could never be > > "\scan_stop:", but either "empty" or contains a list of tokens. So > > "\scan_stop:" means something like \tlp_use:c tried to use a tlp that simply > > doesn't exist > > Oh, of course. I couldn't figure out where the \scan_stop: should > come from. But then I didn't thought about \tlp_use:c. obviously if the tlp has to be constructed first one needs a construction function, so \tlp_use:c is necessary even if one can leave out the \tlp_use:N and from experience if the construction ends up with a previously undeclared tlp then usually things go wrong as it then equals \scan_stop: which is neither expandable (a feature tlps have) nor a "possible" value ie not at all the same as \tlp_new:Nn\l_foo_tlp{} or \tlp_new:Nn\l_foo_tlp{\scan_stop:} so the check and the error message make sense here. cheers frank