User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0)
            Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
References: <m3k34m4vjd.fsf@somewhere.org>
            <5429D0DF.7060608@morningstar2.co.uk> <m3k34lrqkb.fsf@example.com>
Content-Type: text/plain; charset=ISO-8859-1
Message-ID:  <542C1972.5030500@morningstar2.co.uk>
Date:         Wed, 1 Oct 2014 17:10:42 +0200
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: [l3keys] Suggestion: Add a key property for specifying key that /has/ to be used
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <m3k34lrqkb.fsf@example.com>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

On 30/09/2014 19:00, Denis Bitouzé wrote:
>> At present, key properties mainly apply to individual keys in a 'stand
>> alone' sense. This request is different as it's actually about an entire
>> set of keys.
> 
> No, maybe I was unclear: my question concerned the "requireness" of
> a single (or maybe several but treated separately) key property.

I perhaps wasn't clear here. Other properties can be tested by examining
just the key itself, so for example

   foo .value_required:

is tested at the point you do

   foo = <value>

On the other hand, a requirement to set some key can only be tested at
the end of \keys_set:nn, once you know what keys were set. Moreover,
it's potentially ambiguous as

  \keys_set:nn { foo } { required = value }
  \keys_set:nn { foo } { other-key }

doesn't have the "required" key in the second setting: is it required
here or not?
--
Joseph Wright