>> I have a custom class that is based on the memoir class. My question is when should I load memoir? My current structure is:

>>     LoadClass[some options]{memoir}

>>     RequirePackage{several lines of packages}
>>     newcommands defined
>>     newifs defined

>>     DeclareOptionX{lots of options defined} % (using xkeyval)
>>     ProcessOptionsX

>>     memoir settings defined
>>     more local macros defined

>> Now I find I need to create a new option and pass it to memoir, so I'll have to move its loading to after my option processing.

>> Is there any rule about the order in which these things are done? In hindsight I guess that option processing should generally come first.

>> Any rules of thumb about setting up class structure, esp when loading another class?

>> thanks,
>> --Tim Arnold

> Use
> \DeclareOption{memoiroption}{\PassOptionsToClass{memoiroption}{memoir}}

> Then load memoir after option processing, i.e., after \ProcessOptions
> and/or \ExecuteOptions.

> Or, to pass all options you have not otherwise declared:
>    \DeclareOption*{\PassOptionsToClass{\CurrentOption}{memoir}}

> Dan
> To reply by email, change LookInSig to luecking