Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id q4QFGPvT025742 for ; Sat, 26 May 2012 17:16:26 +0200 Received: (qmail 29541 invoked by alias); 26 May 2012 15:16:20 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 26 May 2012 15:16:20 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx068) with SMTP; 26 May 2012 17:16:20 +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 q4QFDscq006835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 May 2012 17:13:54 +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 q4PM1ZB1006546; Sat, 26 May 2012 17:13:53 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1990384 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sat, 26 May 2012 17:13:53 +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 q4QFDrjU011558 for ; Sat, 26 May 2012 17:13:53 +0200 Received: from ix.urz.uni-heidelberg.de (cyrus-portal.urz.uni-heidelberg.de [129.206.100.176]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q4QFDrhQ006824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 26 May 2012 17:13:53 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by ix.urz.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q4QFDqh9012998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 26 May 2012 17:13:53 +0200 Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q4QFCq7F026332 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for ; Sat, 26 May 2012 17:13:46 +0200 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SYIfh-0007Cf-HP for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sat, 26 May 2012 17:12:49 +0200 Received: from 31-19-28-231-dynip.superkabel.de ([31.19.28.231]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 May 2012 17:12:49 +0200 Received: from marco.daniel by 31-19-28-231-dynip.superkabel.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 May 2012 17:12:49 +0200 X-Injected-Via-Gmane: http://gmane.org/ Lines: 54 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 31-19-28-231-dynip.superkabel.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 X-Spam-Flag: No X-Envelope-From: X-Spam-Status: No, hits=-2.10 required=5 tests=BAYES_00,L_P0F_UNKN,SPF_HELO_PASS, SPF_PASS Message-ID: Date: Sat, 26 May 2012 17:12:34 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Marco Daniel Subject: Should l3keys provide a key .initial:n? To: LATEX-L@listserv.uni-heidelberg.de Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p6sJLDpZh614Kjz2nt6F3tHTdDDi9TzotlwOTvXrwLBBI/+AtwvaS/kaYJXZ AOk6TZc//V0/CqvI8ctDxH7BMOgnUJWp5z8EVTeyXDfTWgonVjprWslsfM5p1JSA5MaFxWgfwVBI f0FkhGup2k2DKzAmsNDimA8GOi1wxhkdk24J9xy84eSOibIUChFksw6Rus=V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 7055 Hello, Today I noticed that there is no key .initial:n. This question popped up during writing a small package. Whatever at the moment you have the following possibilities to set a key-value-syntax with an initial value: ======================================================================= %First approach: \keys_define:nn { module } { myoption .int_set:N = \l_modul_myoption_int } \keys_set:nn { module } { myoption = 2 } \ProcessKeysOptions { module } ======================================================================= Second approach \keys_define:nn { module } { myoption .int_set:N = \l_modul_myoption_int , myoption .default:n = 2 } \keys_set:nn { module } { myoption } \ProcessKeysOptions { module } ======================================================================= I suggest to define a new key .initial:n so that we have a third approach: Second approach \keys_define:nn { module } { myoption .int_set:N = \l_modul_myoption_int , myoption .initial:n = 2 } \ProcessKeysOptions { module } ======================================================================= I hope my question is clear. Of course the current methods are separating the definition and setting of keys. In this way it's clear. However I'd prefer the third approach to set an initial value immediately after their definition. What do you think about such a key? regards Marco