57
edits
Changes
Commands with optional arguments (view source)
Revision as of 20:38, 14 August 2021
, 20:38, 14 August 2021Add pitfall with nested macro calls
In ConTeXt, the optional argument processing is handled as a two-step process. \newcommandFirst, we write the command for the end-user as a wrapper command, which calls {\MyCommand{cmd|dosingleempty}}[2][World], {{#2Hello #1!cmd|dodoubleempty}} \MyCommand, {{cmd|dotripleempty}}, ... (from {{\bfseriessrc|syst-aux.mkiv} \MyCommand[Hans]} or {{\scshapesrc|syst-gen.mkii}}) to handle the arguments properly -- including the optional ones -- and then calls a "private" command that contains the internals of the macro. Note that this function call does not explicitly refer to the arguments at all.
\else
World%
\fi
!}
\MyCommand[\bf]\ %
\MyCommand[\sc][Hans]
</context>
If you ''don't'' want any optional arguments, but still want your arguments enclosed in <tt>[]</tt> with appropriate handling for spaces (or line breaks) between the square brackets, use {{cmd|dodoubleargument}} instead of {{cmd|dodoubleempty}}. There are of course versions for other numbers of arguments, found by replacing <tt>double</tt> with <tt>single</tt> through <tt>seventuple</tt>; see {{src|syst-aux.mkiv}} for the exact names.
=== Examples ===
To define <code>\mycommand[#1]{#2}</code> with one optional argument and one mandatory argument, do the following
<context source="yes">
\def\mynewcommand{\dosingleempty\doMyNewCommand}
\def\doMyNewCommand[#1]#2{%
\iffirstargument
There is an optional parameter: {\bf #1}\par%
\else
No optional parameter\par%
\fi
This is the mandatory text: {\em #2}%
}
\starttext
\mynewcommand[opt]{Hello People}
\blank
\mynewcommand{Hello People}
\stoptext
</context>
To define <code>\mycommand[#1][#2]{#3}</code> with two optional arguments and one mandatory argument, do
<texcode>
\def\mycommand{\dodoubleempty\doMycommand}
\def\doMycommand[#1][#2]#3{whatever}
</texcode>
=== Pitfalls ===
==== Passing preceding command's argument ====
Keep in mind that <code>\iffirstargument</code> will always return true if you put before it a command which itself has an argument. See the following example:
<context source="yes" text="produces">
\def\mynewcommand{\dosingleempty\doMyNewCommand}
\def\doMyNewCommand[#1]#2{%
\startalignment[center]
\iffirstargument
There is an optional parameter: {\bf #1}\par%
\else
No optional parameter\par%
\fi
This is the mandatory text: {\em #2}%
\stopalignment
}
\starttext
\mynewcommand[opt]{Hello People}
\blank
\mynewcommand{Hello People}
\stoptext
</context>
Use <code>\doifsomethingelse</code> instead:
<context source="yes" text="This time this is correct:">
\def\mynewcommand{\dosingleempty\doMyNewCommand}
\def\doMyNewCommand[#1]#2{%
\startalignment[center]%
\doifsomethingelse{#1}
{There is an optional parameter: {\bf #1}\par}
{No optional parameter\par}
This is the mandatory text: {\em #2}
\stopalignment%
}
\starttext
\mynewcommand[opt]{Hello People}
\blank
\mynewcommand{Hello People}
\stoptext
</context>
==== Calling the macro from within command arguments (e.g. float title) ====
-- I have no deeper insight yet on the why and neither on which other cases this might apply to, but I hope it may be useful to someone running into errors.
If you wanted to call your macro from within an "argument" such as you would have to with titles or captions in floats:
<texcode>
\startplacefigure[title={We look at \mynewcommand{people} in floats}]
(content)
\stopplacefigure
</texcode>
The above will create a `"\doMyNewCommand doesn't match its definition"` error.
This can be solved by preceding the definition that takes the optional argument with `\unexpanded`:
<texcode>
\unexpanded\def\doMyNewCommand[#1]#2{% ... (etc.)
</texcode>
=== Comparison with LaTeX ===