MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Message-ID:  <CAFUtaNF_feSurGQzLf3TGF6nOPFc8n5H-5AhzCipKQ_PoKF6Kg@mail.gmail.com>
Date:         Tue, 9 Jul 2013 17:36:17 -0400
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: "Joel C. Salomon" <joelcsalomon@GMAIL.COM>
Subject: Using l3keys: choices, property-lists, defaults
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Content-Transfer-Encoding: quoted-printable
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

Folks,

I=E2=80=99ve been following the code changes here, and I=E2=80=99ve asked=
 two
questions on this topic on TeX.SE (=E2=80=9CGenerate l3keys meta key from
subkey=E2=80=9D <http://tex.stackexchange.com/q/120102/2966> and =E2=80=9C=
Can I refer
to key value in general code?=E2=80=9D
<http://tex.stackexchange.com/q/120258/2966>), but I think I need some
direction on this.

Here=E2=80=98s my use-case:  I=E2=80=99ve got a r=C3=A9sum=C3=A9 class wi=
th a set of pre-defined
layout options.  For example, for Constantia I want
    \DeclareDocumentCommand \& {} { \textit { \jcsres_ampersand: } }
while for Fontin I=E2=80=99ve decided on
    \DeclareDocumentCommand \& {} { \textsc { \jcsres_ampersand: } }
instead.  Packages need to be included.  And so on and so forth; there
are between three and fifteen lines of code for each font-set option.

Based on egreg=E2=80=99s suggestion
(http://tex.stackexchange.com/a/120275/2966), my code looks something
like this (or will, when the new Expl3 updates become available):

\bool_if:nTF { \xetex_if_engine_p: || \luatex_if_engine_p: }
  { \clist_const:Nn \c_jcs_fonts_clist { fontin, constantia, lmodern } }
  { \clist_const:Nn \c_jcs_fonts_clist { kpfonts, lmodern } }

\clist_get:NN \c_jcs_fonts_clist \c_jcs_default_font_tl

\keys_define:nn { jcsres }
  {
    font .choices:Vn =3D \c_jcs_fonts_clist
      { \tl_gset:NV \g_jcs_font_option_tl \l_keys_choice_tl },
    font .initial:V =3D \c_jcs_default_font_tl,
    font .value_required,
    font / unknown .code:n =3D
      { \msg_warning:nnn { jcsres } { unknown-font-option } { #1 } }
  }

\msg_new:nnn { jcsres } { unknown-font-option }
  { unknown~font~option~`#1';~using~`\c_jcs_default_font_tl'~instead }

\clist_map_inline:Nn \c_jcs_fonts_clist
  {
    \keys_define:nn { jcsres }
      { #1 .meta:n =3D { font =3D #1 }, #1 .value_forbidden: }
  }

% Somewhere later in the code...
\ProcessKeysOptions { jcsres }

% Somewhere later yet...
\str_case:VnF \g_jcs_font_option_tl
  {
    { fontin } { =E2=80=A6 }
    { constantia } { =E2=80=A6 }
    { lmodern } { =E2=80=A6 }
    { kpfonts } { =E2=80=A6 }
  }
  { \msg_error:nnn { jcsres } { still-unknown-font-option } { #1 } }

\msg_new:nnn { jcsres } { still-unknown-font-option }
  { can't~happen:~unknown~font~option~`#1'. }

This all works, but there=E2=80=99s a fair amount of repetition of inform=
ation.

Bruno has suggested (http://tex.stackexchange.com/a/123201/2966) using
property lists instead.  This feels like a more natural fit for the
problem, and here=E2=80=99s the code I=E2=80=99ve come up with:

\prop_new:N \g_jcs_fontcode_prop

\prop_gput:Nnn \g_jcs_fontcode_prop { lmodern } { =E2=80=A6 }

\bool_if:nT { \xetex_if_engine_p: || \luatex_if_engine_p: }
  { \prop_gput:Nnn \g_jcs_fontcode_prop { fontin } { =E2=80=A6 } }

\bool_if:nT { \xetex_if_engine_p: || \luatex_if_engine_p: }
  { \prop_gput:Nnn \g_jcs_fontcode_prop { constantia } { =E2=80=A6 } }

\bool_if:nF { \xetex_if_engine_p: || \luatex_if_engine_p: }
  { \prop_gput:Nnn \g_jcs_fontcode_prop { kpfonts } { =E2=80=A6 } }

\tl_const:Nx \c_jcs_default_font_tl
  {
    \bool_if:nTF { \xetex_if_engine_p: || \luatex_if_engine_p: }
      { fontin } { kpfonts }
  }

\tl_new:N \l_jcs_fontcode_tl
\keys_define:nn { jcsres }
  {
    font .code:n =3D
      {
        \prop_get:NnNTF \g_jcs_fontcode_prop {#1} \l_jcs_fontcode_tl
          { \tl_gset_eq:NN \g_jcs_fontcode_tl \l_jcs_fontcode_tl }
          {
            \msg_warning:nnn { jcsres } { unknown-font-option } { #1 }
            \prop_get:NVN \g_jcs_fontcode_prop \c_jcs_default_font_tl
\l_jcs_fontcode_tl
            \tl_gset_eq:NN \g_jcs_fontcode_tl \l_jcs_fontcode_tl
          }
      },
    font .value_required:,
    font .initial:V =3D \c_jcs_default_font_tl
   }

\prop_map_inline:Nn \g_jcs_fontcode_prop
  {
    \keys_define:nn { jcsres }
      { #1 .meta:n =3D { font =3D #1 }, #1 .value_forbidden: }
  }

% Somewhere later in the code...
\ProcessKeysOptions { jcsres }
\tl_use:N \g_jcs_fontcode_tl

The trick with copying the code sequence (rather than executing it
within the call to \keys_define) is needed so the default code isn=E2=80=99=
t
run if an option is supplied, or in case the user writes
   \usepackage[font=3Dfontin, font=3Dconstantia]{jcsres}
to execute both conflicting options.

Does this begin to sound like the way forward?

=E2=80=94Joel