On 28-9-2012 14:41, Sietse Brouwer wrote:
Question for the others: What's the difference of \dodoubleargument
and \dodoubleempty? I expected \dodoubleargument to throw an error
since the arguments are supposed to be mandatory.
In MkIV Hans didn’t add this check and in MkII he disabled is for co
>> Question for the others: What's the difference of \dodoubleargument
>> and \dodoubleempty? I expected \dodoubleargument to throw an error
>> since the arguments are supposed to be mandatory.
>
> In MkIV Hans didn’t add this check and in MkII he disabled is for command
> with three or less argume
Am 27.09.2012 um 18:16 schrieb Marco Patzer :
> Question for the others: What's the difference of \dodoubleargument
> and \dodoubleempty? I expected \dodoubleargument to throw an error
> since the arguments are supposed to be mandatory.
In MkIV Hans didn’t add this check and in MkII he disabled
2012-09-27 Sietse Brouwer :
Hi Sietse,
> As I understand it, \define[2] is preferred over \def#1#2 because it
> refuses to overwrite existing commands.
\define overwrites existing commands with pleasure. In contrast to
\def it prints a message to the log file: “\mycommand is already
defined”.
>
On 09/27/2012 05:45 PM, Sietse Brouwer wrote:
Hi all,
As I understand it, \define[2] is preferred over \def#1#2 because it
refuses to overwrite existing commands.
\define[2]\mycommand{code code code}
defines a command to be invoked with
\mycommand{...}{...}
Can I use \define, or a related comm
Hi all,
As I understand it, \define[2] is preferred over \def#1#2 because it
refuses to overwrite existing commands.
\define[2]\mycommand{code code code}
defines a command to be invoked with
\mycommand{...}{...}
Can I use \define, or a related command, to define a command that
takes square-brack
