User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0
MIME-Version: 1.0
References: <m3k34m4vjd.fsf@somewhere.org>           
            <5429D0DF.7060608@morningstar2.co.uk> <m3k34lrqkb.fsf@example.com> 
            <10k836fpz0maa.dlg@nililand.de> <m3lhozrgp6.fsf@example.com>       
            <zqejj1e7vcjn$.dlg@nililand.de> <m34mvnre7x.fsf@example.com>
            <1p1jnnjmq41l6.dlg@nililand.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Message-ID:  <542D37EA.1080101@free.fr>
Date:         Thu, 2 Oct 2014 13:32:58 +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: "Julien RIVAUD (_FrnchFrgg_)" <frnchfrgg@FREE.FR>
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:  <1p1jnnjmq41l6.dlg@nililand.de>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Content-Transfer-Encoding: 8bit
Status: R

Le 02/10/2014 09:22, Ulrike Fischer a écrit :

> Beside this there is also the timing problem Joseph mentioned: when
> should be tested if a key has been used? It is obviously not the key
> code of the key that can do it. So imho you are not looking for a
> .required property but a .enableifsettest property which adds and
> sets some boolean which you can later check.

Or better yet, use an initial value for your property that unambiguously 
represents "not set", and validate that at the beginning.

Since you need to have an extra step to check if the required properties 
have been set, you can as well use a token list to store the value 
instead of directly an int for instance, and first check if it is your 
special "not set" value, then cast it to integer yourself.

Julien "_FrnchFrgg_" Rivaud