LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 17 Jul 2013 18:27:37 +0000
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Message-ID: <[log in to unmask]>
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: "Joel C. Salomon" <[log in to unmask]>
Parts/Attachments: text/plain (16 lines)
Joseph Wright <joseph.wright@...> writes:
> At present I'm waiting to see what people thing of the code-level stuff.
> At the same time, I'm not sure about making package option processing
> too complex. The lesson I've learned is that keyval in options is
> governed by the LaTeX2e kernel: options are expanded, and checking for
> clashes doesn't 'know' about keyval. Thus I tend to think load-time
> options should really be limited to things that need to happen there,
> with later \<thing>setup to cover more complex option sets.

Is the behavior of package & class options expected to be different 
(specifically, keyval-aware) in a LaTeX3 kernel?  If so, would it be 
appropriate to define \UseExplPackage et al. so that the future behavior can 
be experimented with?