References: <11lm3sqjz6xux$.dlg@nililand.de>
            <5595661F.1070304@morningstar2.co.uk>
            <CA+jHFwSTVzJ4VYb9tF5n2tgX1hU821hG32_JKQLBfWVZ=SnxTQ@mail.gmail.com> <55962878.5030204@morningstar2.co.uk>
            <bbkmg4gzwky6.dlg@nililand.de>
            <55A4A8D2.6060304@morningstar2.co.uk>
            <1bc6qigbj7juc.dlg@nililand.de>
            <55A4CB65.9050302@morningstar2.co.uk>
            <1nk3r88bkot3p$.dlg@nililand.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
            Thunderbird/38.0.1
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Message-ID:  <55A4DE6A.4010307@morningstar2.co.uk>
Date:         Tue, 14 Jul 2015 11:03:22 +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: Order of key declarations
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <1nk3r88bkot3p$.dlg@nililand.de>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 14/07/2015 10:19, Ulrike Fischer wrote:
> Am Tue, 14 Jul 2015 09:42:13 +0100 schrieb Joseph Wright:
> 
>> I was thinking of
>>
>>     \keys_define:nn {test}
>>       {
>>         testa .code:n = {\tl_show:n {#1}},
>>         testa .value_required:,
>>         testb .code:n = {\tl_show:n {#1}},
>>         testb .value_required:,
>>         testb .default:n = {}
>>     }
>>
>>     \keys_set:nn {test} {testa,testb}
>>
>> where one might expect to get an error only in the first case. That's
>> not currently the situation!
> 
> Hm. My first reaction was that it works as expected. If I explictly
> require that the *user* gives a value, a *package* default doesn't
> make sense and shouldn't replace the user action.

That's entirely logical and as you say what currently happens, it's just
it's not documented (or I think tested). I'll address that so we have a
clear position :-)

> It is also consistent with the other way round:
> 
> \documentclass{article}
> \usepackage{expl3}
> \begin{document}
> \ExplSyntaxOn
>   \keys_define:nn {test}
>       {
>         testb .code:n = {#1},
>         testb .value_forbidden:,
>         testb .default:n = {xxx}
>     }
> 
>    \keys_set:nn {test} {testb}
> 
> \end{document} 

Again, probably should document this.

Time-allowing I will do an update to l3keys today to address all of the
points raised.
--
Joseph Wright