Return-Path: Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 22 Aug 2011 19:16:53 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx047) with SMTP; 22 Aug 2011 21:16:53 +0200 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 p7MJERIK028819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2011 21:14:27 +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 p7MFBwCg029851; Mon, 22 Aug 2011 21:14:27 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1592086 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 22 Aug 2011 21:14:27 +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 p7MJER92023276 for ; Mon, 22 Aug 2011 21:14:27 +0200 Received: from anchor-post-2.mail.demon.net (anchor-post-2.mail.demon.net [195.173.77.133]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id p7MJEGwE011353 for ; Mon, 22 Aug 2011 21:14:19 +0200 Received: from cremornelane.demon.co.uk ([80.177.25.195] helo=palladium.local) by anchor-post-2.mail.demon.net with esmtp (Exim 4.69) id 1QvZwt-0002q8-m8 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 22 Aug 2011 19:14:16 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 References: <4E4FF538.7070601@morningstar2.co.uk> <9788A2B7-3E8F-4D2C-A52E-10999BCB59FA@gmail.com> <4E516DF2.4040002@morningstar2.co.uk> <104nbkj0nr84x.dlg@nililand.de> <4E523217.2080408@morningstar2.co.uk> X-Enigmail-Version: 1.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4E52AA87.6090608@morningstar2.co.uk> Date: Mon, 22 Aug 2011 20:14:15 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: couple of l3keys notes To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antivirus: 0 (no virus found) X-GMX-Antispam: 5 (BackTrace mail analyze); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnGL2vqOgpaBYL16oitsMrgDt/NQNpSCZF7bt5n WT2HM38qZ+yU5w+iPv6yGKzGNRa0WQlhvTMzEO1AERl8LpkYQ==V1; Status: R X-Status: X-Keywords: X-UID: 6820 On 22/08/2011 13:28, Ulrike Fischer wrote: > Am Mon, 22 Aug 2011 11:40:23 +0100 schrieb Joseph Wright: > > >> Now while this is okay, the point I guess is that a cleaner interface is >> desirable. One simple approach would be to define \keys_set_known:nn, >> which does the same as \keys_set:nn but (a) raises no error for unknown >> keys and (b) stores unknowns in some defined place. This might lead to >> >> \keys_set_known:nn { chess / init } {#1} >> \keys_set_known:nV { chess / set } \l_keys_unknown_keyvals_clist >> \keys_set:nV { chess / fill } \l_keys_unknown_keyvals_clist >> >> (I'm imagining \l_keys_unknown_keyvals_clist contains the keys plus >> values, with \l_keys_unknown_keys_clist just containing the key names.) >> >> An obvious question then is whether to provide an 'internal' recycle, >> similar to \setrmkeys, or just to provide the list as a variable and >> leave it to the programmer to do the recycling. > > I think I would prefer a list, it's more flexible (and easier to > inspect if something goes wrong). I have added the scheme broadly as outlined above to l3keys. Feedback would be welcome. For example, does 'set_known' convey the appropriate idea? Show the variable used for storing the 'return' value be fixes, or flexible as in \keys_set_known:nnN { } { } -- Joseph Wright