Syntax for `NewDocumentCommand`
up vote
5
down vote
favorite
The xparse documentation gives examples of names of NewDocumentCommands enclosed in braces, and without braces, as demonstrated in the two commands below. Is there any difference in functionality whatsoever between the two? I never use braces and better be safe than sorry.
documentclass{article}
%=======================
usepackage{xparse}
%-----------------------
ExplSyntaxOn
NewDocumentCommandmyExp{m}{#1}
NewDocumentCommand{myExpAlt}{m}{#1}
ExplSyntaxOff
%-----------------------
begin{document}
myExp{101}
myExpAlt{123}
end{document}
xparse
asked 1 hour ago
Reinhard Neuwirth
1,52211322
add a comment |
up vote
5
down vote
favorite
The xparse documentation gives examples of names of NewDocumentCommands enclosed in braces, and without braces, as demonstrated in the two commands below. Is there any difference in functionality whatsoever between the two? I never use braces and better be safe than sorry.
documentclass{article}
%=======================
usepackage{xparse}
%-----------------------
ExplSyntaxOn
NewDocumentCommandmyExp{m}{#1}
NewDocumentCommand{myExpAlt}{m}{#1}
ExplSyntaxOff
%-----------------------
begin{document}
myExp{101}
myExpAlt{123}
end{document}
xparse
asked 1 hour ago
Reinhard Neuwirth
1,52211322
2
In your example, there is no need forExplSyntaxOn...ExplSyntaxOff.
– Werner
1 hour ago
add a comment |
up vote
5
down vote
favorite
up vote
5
down vote
favorite
The xparse documentation gives examples of names of NewDocumentCommands enclosed in braces, and without braces, as demonstrated in the two commands below. Is there any difference in functionality whatsoever between the two? I never use braces and better be safe than sorry.
documentclass{article}
%=======================
usepackage{xparse}
%-----------------------
ExplSyntaxOn
NewDocumentCommandmyExp{m}{#1}
NewDocumentCommand{myExpAlt}{m}{#1}
ExplSyntaxOff
%-----------------------
begin{document}
myExp{101}
myExpAlt{123}
end{document}
xparse
asked 1 hour ago
Reinhard Neuwirth
1,52211322
The xparse documentation gives examples of names of NewDocumentCommands enclosed in braces, and without braces, as demonstrated in the two commands below. Is there any difference in functionality whatsoever between the two? I never use braces and better be safe than sorry.
documentclass{article}
%=======================
usepackage{xparse}
%-----------------------
ExplSyntaxOn
NewDocumentCommandmyExp{m}{#1}
NewDocumentCommand{myExpAlt}{m}{#1}
ExplSyntaxOff
%-----------------------
begin{document}
myExp{101}
myExpAlt{123}
end{document}
xparse
xparse
asked 1 hour ago
Reinhard Neuwirth
1,52211322
asked 1 hour ago
Reinhard Neuwirth
1,52211322
asked 1 hour ago
Reinhard Neuwirth
1,52211322
asked 1 hour ago
Reinhard Neuwirth
1,52211322
asked 1 hour ago
Reinhard Neuwirth
1,52211322
1,52211322
2
In your example, there is no need forExplSyntaxOn...ExplSyntaxOff.
– Werner
1 hour ago
add a comment |
2
In your example, there is no need forExplSyntaxOn...ExplSyntaxOff.
– Werner
1 hour ago
2
2
In your example, there is no need for
ExplSyntaxOn...ExplSyntaxOff.– Werner
1 hour ago
In your example, there is no need for
ExplSyntaxOn...ExplSyntaxOff.– Werner
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
There is no difference, similar to the notation used with newcommand and friends, as long as you pass it a control sequence. Technically you're passing an argument to newcommand, which is then set using def internally, so you should use {<csname>}. However, if you don't use braces, the first token is grabbed.
answered 1 hour ago
Werner
434k619531638
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use{<csname>}.
– Reinhard Neuwirth
39 mins ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
There is no difference, similar to the notation used with newcommand and friends, as long as you pass it a control sequence. Technically you're passing an argument to newcommand, which is then set using def internally, so you should use {<csname>}. However, if you don't use braces, the first token is grabbed.
answered 1 hour ago
Werner
434k619531638
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use{<csname>}.
– Reinhard Neuwirth
39 mins ago
add a comment |
up vote
5
down vote
accepted
There is no difference, similar to the notation used with newcommand and friends, as long as you pass it a control sequence. Technically you're passing an argument to newcommand, which is then set using def internally, so you should use {<csname>}. However, if you don't use braces, the first token is grabbed.
answered 1 hour ago
Werner
434k619531638
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use{<csname>}.
– Reinhard Neuwirth
39 mins ago
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
There is no difference, similar to the notation used with newcommand and friends, as long as you pass it a control sequence. Technically you're passing an argument to newcommand, which is then set using def internally, so you should use {<csname>}. However, if you don't use braces, the first token is grabbed.
answered 1 hour ago
Werner
434k619531638
There is no difference, similar to the notation used with newcommand and friends, as long as you pass it a control sequence. Technically you're passing an argument to newcommand, which is then set using def internally, so you should use {<csname>}. However, if you don't use braces, the first token is grabbed.
answered 1 hour ago
Werner
434k619531638
answered 1 hour ago
Werner
434k619531638
answered 1 hour ago
Werner
434k619531638
answered 1 hour ago
Werner
434k619531638
434k619531638
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use{<csname>}.
– Reinhard Neuwirth
39 mins ago
add a comment |
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use{<csname>}.
– Reinhard Neuwirth
39 mins ago
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use
{<csname>}.– Reinhard Neuwirth
39 mins ago
Reassuring that there is no harm in not using braces, but formal correctness would dictate to use
{<csname>}.– Reinhard Neuwirth
39 mins ago
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f464075%2fsyntax-for-newdocumentcommand%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
In your example, there is no need for
ExplSyntaxOn...ExplSyntaxOff.– Werner
1 hour ago