xparse g argument should be avoided?
up vote
0
down vote
favorite
In new versions of xparse
the manual states the following: (in 2. Backwards Compatibility)
One role of xparse is to describe existing LaTeX interfaces, including some that are rather unusual in LaTeX (as opposed to formats such as plain TeX) such as delimited arguments. As such, the package defines some argument specifiers that should largely be avoided nowadays as using them in packages leads to inconsistent user interfaces. The simplest syntax is often best, with argument specifications such as mmmm or ommmm (...)
What kind of problems like that 'inconsistent user interfaces' might exhibit using for example g-parameter or G-parameter?
I'm the author of a class that rely on macros based on these parameters and would be good knowing if authors of LaTeX3'xparse
will drop the support of these parameters or what issues on which circumstances might exhibit...
latex3 xparse parameters newdocumentcommand
add a comment |
up vote
0
down vote
favorite
In new versions of xparse
the manual states the following: (in 2. Backwards Compatibility)
One role of xparse is to describe existing LaTeX interfaces, including some that are rather unusual in LaTeX (as opposed to formats such as plain TeX) such as delimited arguments. As such, the package defines some argument specifiers that should largely be avoided nowadays as using them in packages leads to inconsistent user interfaces. The simplest syntax is often best, with argument specifications such as mmmm or ommmm (...)
What kind of problems like that 'inconsistent user interfaces' might exhibit using for example g-parameter or G-parameter?
I'm the author of a class that rely on macros based on these parameters and would be good knowing if authors of LaTeX3'xparse
will drop the support of these parameters or what issues on which circumstances might exhibit...
latex3 xparse parameters newdocumentcommand
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In new versions of xparse
the manual states the following: (in 2. Backwards Compatibility)
One role of xparse is to describe existing LaTeX interfaces, including some that are rather unusual in LaTeX (as opposed to formats such as plain TeX) such as delimited arguments. As such, the package defines some argument specifiers that should largely be avoided nowadays as using them in packages leads to inconsistent user interfaces. The simplest syntax is often best, with argument specifications such as mmmm or ommmm (...)
What kind of problems like that 'inconsistent user interfaces' might exhibit using for example g-parameter or G-parameter?
I'm the author of a class that rely on macros based on these parameters and would be good knowing if authors of LaTeX3'xparse
will drop the support of these parameters or what issues on which circumstances might exhibit...
latex3 xparse parameters newdocumentcommand
In new versions of xparse
the manual states the following: (in 2. Backwards Compatibility)
One role of xparse is to describe existing LaTeX interfaces, including some that are rather unusual in LaTeX (as opposed to formats such as plain TeX) such as delimited arguments. As such, the package defines some argument specifiers that should largely be avoided nowadays as using them in packages leads to inconsistent user interfaces. The simplest syntax is often best, with argument specifications such as mmmm or ommmm (...)
What kind of problems like that 'inconsistent user interfaces' might exhibit using for example g-parameter or G-parameter?
I'm the author of a class that rely on macros based on these parameters and would be good knowing if authors of LaTeX3'xparse
will drop the support of these parameters or what issues on which circumstances might exhibit...
latex3 xparse parameters newdocumentcommand
latex3 xparse parameters newdocumentcommand
asked 10 mins ago
Emilio Lazo
42229
42229
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f463626%2fxparse-g-argument-should-be-avoided%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