Document Classes ⇒ Weird interaction between packages and my document class

[rspringuel]

So, I've written a document class, based on the report class, which is designed to format a document according to my school's thesis guidelines (well, part written, part inherited). It's been working just fine for a while now, but I just came across an interesting error (and by "interesting" I mean one I can't figure out). It seems that hyperref and ifthen don't like working together when the \equal command gets called inside a sectioning command (level of the command doesn't matter). The error from the log file is:

Code: Select all

1
2
3
4
./Main.tex:22: Undefined control sequence.
<argument> \equal 
                  {1}{1}
l.22 \subsubsection{\protect\combine{1}}
 
 
הההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההה
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

which is what I'd expect if ifthen wasn't loaded. Not loading the hyperref package causes the error to go away, as does switching the document class to report. The error also goes away if my \combine command doesn't call the \equal command. Any ideas on what kind of interaction might be causing this behavior.

Attached is a MWE which also contains my class file.

[Juanjo]

Instead of bothering finding the cause of the problem, I propose this alternative definition of \combine. It works for me.

Code: Select all

Code, edit and compile here:

1
2
3
4
5
6
7
\newcommand{\combine}[1]{%
   \ifcase#1 \or \textit{Correct}
             \or $F \propto v$
             \or \textit{Formal}
             \or \textit{Naive}
             \or \textit{Newton's 3rd}
    \fi}
 
 
הההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההההה
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Run LaTeX here

[rspringuel]

That does indeed work for me too. It bugs my perfectionist side to not know what was causing the original problem, but my practical side says that at this point in the thesis writing process it's far more important to have a working solution rather than understanding the problem.

Thanks.

[localghost]

If that solves the problem, please be so kind and mark the topic accordingly as described in Section 3 of the Board Rules.


Best regards
Thorsten

[rspringuel]

I'll mark it as solved, but really that's more of a work around rather than a solution. Under other circumstances, (if my shorthand wasn't integers) the problem would still exist.