LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
Date: Wed, 1 Oct 2014 17:10:42 +0200
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID: <[log in to unmask]>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
In-Reply-To: <[log in to unmask]>
Content-Type: text/plain; charset=ISO-8859-1
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (29 lines)
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

ATOM RSS1 RSS2