LATEX-L Archives

Mailing list for the LaTeX3 project


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: Thu, 2 Oct 2014 13:32:58 +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=utf-8; format=flowed
From: "Julien RIVAUD (_FrnchFrgg_)" <[log in to unmask]>
Parts/Attachments: text/plain (18 lines)
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