LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Subject:
From:
Joseph Wright <[log in to unmask]>
Reply To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Mon, 31 Aug 2009 20:26:43 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Manuel Pégourié-Gonnard wrote:
> Hi all,
> 
> Is their a practical way to create key=value options for a 2e packages using the
> new material from expl3, or should I stick to xkeyval for this atm? After
> quickly reading the doc of l3keyval and l3keys, I think I'll have to stick to
> xkeyval, but I prefer asking in case I missed something.
> 
> Thanks,
> Manuel (about to start his first package in expl3).
> 

Hello Manuel,

I've put together a package which does what you want. For the moment
it's called "l3keys2e" and is now on the SVN, but before I send the code
to CTAN a better name might be nice :-)

It provides one function, which again might need a better name. For the
moment, it is called \ProcessKeysOptions, and takes one argument:

\keys_define:nn { module } { <keys> }
\ProcessKeysOptions { module }

In the LaTeX3 "spirit", I've stuck with a fixed number of mandatory
arguments here (i.e. there is no star version, unlike pgfopts which is
the pgfkeys version I wrote a while ago).
-- 
Joseph Wright

ATOM RSS1 RSS2