Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Nov 2009 17:27:05 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id nAOGR26I003536 for ; Tue, 24 Nov 2009 17:27:02 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id nAOGMDp9015482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Nov 2009 17:22:13 +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 nAOEDAve009326; Tue, 24 Nov 2009 17:22:09 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 370185 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 24 Nov 2009 17:22:09 +0100 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 nAOGM96s026601 for ; Tue, 24 Nov 2009 17:22:09 +0100 Received: from pluto.open.ac.uk (pluto.open.ac.uk [137.108.145.32]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id nAOGLw1j015105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 24 Nov 2009 17:22:02 +0100 Received: from laurel.open.ac.uk ([137.108.170.71]) by pluto.open.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NCy9O-0004rE-CX for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 24 Nov 2009 16:21:58 +0000 Received: from KIELDERCMS1.open.ac.uk ([137.108.140.185]) by LAUREL.open.ac.uk ([137.108.170.71]) with mapi; Tue, 24 Nov 2009 16:21:58 +0000 Thread-Topic: Passing a dictionary to, for example, the TOC entry formatter Thread-Index: AcptFV3X9+SBE4l3Rtmyjj6D2AVYWgADEoGQ References: <19209.8773.325233.396932@morse.mittelbach-online.de> <4B0BDBC8.3060802@morningstar2.co.uk> <4B0BF1A9.3030507@morningstar2.co.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.uni-heidelberg.de id nAOGM96s026602 Message-ID: Date: Tue, 24 Nov 2009 16:21:58 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: "J.Fine" Subject: Re: Passing a dictionary to, for example, the TOC entry formatter To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <4B0BF1A9.3030507@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -6.599 () BAYES_00,RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 24 Nov 2009 16:27:06.0013 (UTC) FILETIME=[F62FE4D0:01CA6D22] Status: R X-Status: X-Keywords: X-UID: 6184 Joseph wrote: > I think that it's likely that dictionaries will be implemented using > data "packed" inside another variable, rather than as csnames. This > makes it easier to do things like "clear the dictionary" without needing > to know every entry type. Ah. So something like \def\mydict{\@@dict{ \@item{apple}{Jonathan}% \@item{plum}{Victoria}% }} If you have to program this sort of thing in TeX, something like this may be a good idea. But I don't think programming everything in TeX is a good idea. Will LaTeX3 provide a DOM? Programmed in TeX macros? -- Jonathan The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).