Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Nov 2009 14:15:45 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nAODFgxV028383 for ; Tue, 24 Nov 2009 14:15:42 +0100 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 nAODD7jA012396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Nov 2009 14:13:07 +0100 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 nAOAVw67020225; Tue, 24 Nov 2009 14:13:01 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 366816 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 24 Nov 2009 14:13:01 +0100 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 nAODD1Ms031270 for ; Tue, 24 Nov 2009 14:13:01 +0100 Received: from ueamailgate01.uea.ac.uk (ueamailgate01.uea.ac.uk [139.222.131.184]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id nAODCgJh020414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 24 Nov 2009 14:12:48 +0100 Received: from ueams02.uea.ac.uk (ueams02.uea.ac.uk [139.222.131.131]) by ueamailgate01.uea.ac.uk (8.13.1/8.13.1) with ESMTP id nAODCfwv019278 for ; Tue, 24 Nov 2009 13:12:41 GMT Received: from [139.222.201.77] by ueams02.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NCvCD-0003Qa-SY for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 24 Nov 2009 13:12:41 +0000 User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 References: <19209.8773.325233.396932@morse.mittelbach-online.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Canit-CHI2: 0.01 X-Bayes-Prob: 0.0001 (Score 0, tokens from: @@RPTN, outgoing) X-CanItPRO-Stream: UEA:outgoing (inherits from UEA:default,base:default) X-Canit-Stats-ID: 36488604 - 112f291f351f X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 X-Scanned-By: CanIt (www . roaringpenguin . com) on 139.222.131.184 Message-ID: <4B0BDBC8.3060802@morningstar2.co.uk> Date: Tue, 24 Nov 2009 13:12:40 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: Passing a dictionary to, for example, the TOC entry formatter To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 24 Nov 2009 13:15:45.0670 (UTC) FILETIME=[3B5E9260:01CA6D08] Status: R X-Status: X-Keywords: X-UID: 6181 J.Fine wrote: > Frank: I don't understand what you mean by 'the overhead of processing'.) I assume Frank was thinking that we wouldn't want to do everything in a dictionary manner as some arguments are always needed, and so something like: \def\foo@bar#1#2{% Title: #1\\% Name: \DictionaryLookup{#2}{name}\\% Address: \DictionaryLookup{#2}{address}\\% } will be faster for the explicitly passed #1 than the dictionary items, independent of how the dictionary is implemented. (I'd assume that a dictionary would be a single data structure: I'd probably do it as an expl3 properly list, and then recovering data would certainly add some processing overhead. However, even a csname expansion as you outline is an additional overhead compared to an explicitly passed value.) -- Joseph Wright