Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Wed, 17 Jun 2009 18:59:02 +0200 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n5HGx2Nc001346 for ; Wed, 17 Jun 2009 18:59:02 +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 n5HGpHem005306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jun 2009 18:51:18 +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 n5HG00jY030742; Wed, 17 Jun 2009 18:51:16 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 291681 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 17 Jun 2009 18:51:16 +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 n5HGpGdL013814 for ; Wed, 17 Jun 2009 18:51:16 +0200 Received: from mailgate5.uea.ac.uk (mailgate5.uea.ac.uk [139.222.130.185]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id n5HGp6U9024212 for ; Wed, 17 Jun 2009 18:51:10 +0200 Received: from [139.222.131.131] (helo=ueams02.uea.ac.uk) by mailgate5.uea.ac.uk with esmtp (Exim 4.50) id 1MGyLq-0002qx-6n for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 17 Jun 2009 17:51:06 +0100 Received: from [139.222.114.191] by ueams02.uea.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MGyLm-0002PN-Ql for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 17 Jun 2009 17:51:02 +0100 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 References: <4A2F5FE3.3030205@morningstar2.co.uk> <4A300B9E.4000608@morningstar2.co.uk> <8C8871A5-B9AF-4EF4-8AAA-F282C1D206A0@gmail.com> <4A30C022.8000201@morningstar2.co.uk> <4A30E83D.3070902@morningstar2.co.uk> <4A31233E.50801@morningstar2.co.uk> <4A32CD74.2040709@morningstar2.co.uk> <16D7A843-1CB1-40A8-9092-8CD795670107@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4A391EFD.7020003@morningstar2.co.uk> Date: Wed, 17 Jun 2009 17:51:09 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: Key-value input To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <16D7A843-1CB1-40A8-9092-8CD795670107@gmail.com> 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: 17 Jun 2009 16:59:02.0940 (UTC) FILETIME=[EAABBDC0:01C9EF6C] Status: R X-Status: X-Keywords: X-UID: 5798 Hello Will, > This looks really nice to me. I think it is more useable and perhaps > more useful to have "real names" for the different types of key, and as > mentioned having a separate key for a default value is very nice for > later customisation. Thanks for that :-) I'd agree, hence my continued work on the keys3 idea. I hope that is now getting toward the point where is really does point to a way to implement a general keyval creation system in LaTeX3. One thing to notice about template (which I've only just discovered myself) is that the "default" arguments it creates: key =n [default] \l_some_tl are not defaults in the (x)keyval/kvoptions/pgfkeys/key3 sense. In template, this is the value initially assigned to a key before processing, whereas in the other systems a default is what is used if only the key name is given. More on that to follow as I sort it out! Joseph