Lines: 44
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
User-Agent: 40tude_Dialog/2.0.15.41de
Message-ID:  <11lm3sqjz6xux$.dlg@nililand.de>
Date:         Thu, 2 Jul 2015 15:43:38 +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: Ulrike Fischer <news3@NILILAND.DE>
Subject: Order of key declarations
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

I had problems with some keys because I hadn't really paid attention
to the order of the declaration. Some tests revealed then that some
key properties (e.g. .code:n) overwrite other (e.g. .groups:n and
.default:n). I don't know if it is a bug but imho at least it should
be mentioned in the documentation.

\documentclass[parskip]{scrartcl}

\usepackage{expl3}
\begin{document}
\ExplSyntaxOn

\keys_define:nn{test}
 {
  key .code:n    = {show~key~(#1)~},
  key .groups:n  = {show},
  key .default:n = {XX},  
  %different order:
  keyb .groups:n  = {show},
  keyb .default:n = {XX},
  keyb .code:n    = {show~keyb~(#1)},  
 }

Key:~\keys_set:nn{test}{key,keyb}~\\
Group:~\keys_set_groups:nnn {test} {show} {key=A,keyb=A}

% a change of the .code:n property
\par    
\keys_define:nn{test}
 {
  key .code:n    = {show~key~(#1)},
 }

Key:~\keys_set:nn{test}{key}~\\
Group:~\keys_set_groups:nnn {test} {show} {key=B}
\ExplSyntaxOff

\end{document}


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/