User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0)
            Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
References: <jpqrt2$vk7$1@dough.gmane.org>
            <4FC13326.1060904@morningstar2.co.uk>
            <CANQYN6x1+vdR1gFFHwvtRnX1o2nm-JKByie4tvV6U-eDsZHdUA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-ID:  <4FC1D7A0.6020705@morningstar2.co.uk>
Date:         Sun, 27 May 2012 08:28:32 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@listserv.uni-heidelberg.de>
Sender: Mailing list for the LaTeX3 project <LATEX-L@listserv.uni-heidelberg.de>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Should l3keys provide a key .initial:n?
To: LATEX-L@listserv.uni-heidelberg.de
In-Reply-To:  <CANQYN6x1+vdR1gFFHwvtRnX1o2nm-JKByie4tvV6U-eDsZHdUA@mail.gmail.com>
Precedence: list
Status: R

On 26/05/2012 23:06, Bruno Le Floch wrote:
> I'm no keys expert, but couldn't
> 
>   \int_set:Nn \l_modul_myoption_int { 2 }
> 
> do the job, at least in this case?
> 
> Cheers,
> Bruno

Yes it would. The question here is mainly conceptual: setting up key
defaults using a keyval interface rather than whatever is the underlying
implementation. That's more noticeable with a key which is attached to
arbitrary code, for example a multiple choice or .code:n key.
-- 
Joseph Wright