Message-Id: <199402111150.AA21287@mail.cs.tu-berlin.de>
Reply-To: Mailing list for the LaTeX3 project <LATEX-L@DHDURZ1.BITNET>
In-Reply-To:  <m0pUw8A-0006QxC@rsuna.crn.cogs.susx.ac.uk> (message from Joachim
              Schrod on Fri, 11 Feb 1994 12:20:39 +0100)
Date:         Fri, 11 Feb 1994 11:45:00 GMT
From: Alan Jeffrey <alanje@COGS.SUSSEX.AC.UK>
Sender: Mailing list for the LaTeX3 project <LATEX-L@DHDURZ1.BITNET>
To: Multiple recipients of list LATEX-L <LATEX-L@DHDURZ1.BITNET>
Subject:      Re: On compatibility in LaTeX2e [was: Re: keyed options lis
Status: R

> With hard-wired limited options?

The options are only as hard-wired as the class-writer wants them to
be.  If you say:

   \DeclareOption*{\myoptionparser}

then your option parser can do what it likes with \CurrentOption.  For
example:

\def\myoptionparser{%
   \expandafter\@myoptionparser\CurrentOption==\@myoptionparser%
}

\def\@myoptionparser#1=#2=#3\@myoptionparser{%
   ... do something with keyword #1 = value #2 ...
}

And voila, you've got keyword=value options.

Whether you'd actually *want* keyword=value options is another
matter...

Alan.