Jtdylktuy

I am trying to define a new command, but specifying the new control string "on the fly" using csname and endcsname. (This is for the purpose of implementing a dependency injection pattern.) **Alternatively, is there a way of doing this with expl3?

Normally, I have been using expandafternewcommand ... but in this use case, I would like to define the csname WITHIN newcommand's first parameter, like so:

newcommand{expandbeforecsname GetCommandName endcsname}[1]{small I did it!!!}

newcommandexpandbeforecsname GetCommandName endcsname{small I did it again!!!}

I would like for everything within the braces to be expanded BEFORE newcommand - but without relying on expandafter before newcommand.

Issues:

• I am curious as to whether there is a normal way of doing this in LaTeX, without having to rely on another process input buffer hack, (with Lua).




• Adding expandafter, nameuse, edef, let, csname, etc, within the newcommand's parameter just results in an error to redefine those commands. (Even if in {} or begingroup closures.




• Trying to meaning expandafter to figure out how it works fails, (predictably, and funny too).

I (with slight modifications) quote my answer to the question Define a control sequence after that a space matters as it seems to apply to your question as well:

By applying the #{-notation, you can define macros whose last argument is delimited by an opening brace. Unlike with other argument delimiters that get removed when gathering arguments, TeX will leave a delimiting opening brace in place.

(Actually the mechanism isn't restricted to opening brace character tokens. You can use any token whose category code is 1 at definition time. Could as well be #WeIrd after letWeIrd={  .)

Delimited arguments can be empty.

Therefore for obtaining a control sequence token from a set of tokens that expands to a set of character tokens which forms the name of the control sequence token in question both for defining and for calling that control sequence token, you can (by applying the #{-notation) invent a single control sequence name which processes a brace delimited argument trailed by an undelimited argument (which is nested in braces). After having TeX fetch the arguments, you can have TeX whirl them around and apply csname..endcsname to the argument supplied inside braces. The name of the control sequence token in question can contain space tokens as well.

makeatletter

%

newcommandname{}%

longdefname#1#{UD@innername{#1}}%

%

newcommandUD@innername[2]{%

  expandafterUD@exchangeexpandafter{csname#2endcsname}{#1}%

}%

%

newcommandUD@exchange[2]{#2#1}%

%

makeatother

name foo{bar} → expansion step 1:
UD@innername{foo}{bar} → expansion step 2:
expandafterUD@exchangeexpandafter{csname barendcsname}{foo} → expansion step 3:
UD@exchange{bar}{foo} → expansion step 4:
foobar  .

In expansion contexts you would need four expandafter-chains for obtaining the result.

As romannumeral does not produce any token when encountering a non-positive number, you can add a bit of romannumeral-expansion in order to reduce the amount of expandafter-chains.

Either do romannumeralname0 foo{bar}. This way only one expandafter-chain hitting the romannumeral-token is needed.

Or have the romannumeral-expansion "hardcoded" within the definition—this way two expandafter-chains are needed. The first one for obtaining the topl-level-expansion of name. The second one for inducing romannumeral-expansion.

makeatletter

%

newcommandname{}%

longdefname#1#{romannumeral0UD@innername{#1}}%

%

newcommandUD@innername[2]{%

  expandafterUD@exchangeexpandafter{csname#2endcsname}{ #1}%

}%

%

newcommandUD@exchange[2]{#2#1}%

%

makeatother

With such a macro you are not bound to specific definition commands:

name{foo} → foo  .    (←This is the way in which you do not define but just call/use control-sequences by means of name.)

namenewcommand{foo} → newcommandfoo  .

nameDeclareRobustCommand{foo} → DeclareRobustCommandfoo  .

namegloballongouterdef{foo} → globallongouterdeffoo  .

nameexpandafter{foo}bar → expandafterfoobar  .

namelet{foo}=bar → letfoo=bar  .

namestring{foo} → stringfoo  .

namemeaning{foo} → meaningfoo  .

You can as well use such a macro for defining/calling macros whose names
contain spaces:

name{foo } → foo␣  .

namenewcommand{foo } → newcommandfoo␣  .

nameDeclareRobustCommand{foo } → DeclareRobustCommandfoo␣  .

namegloballongouterdef{foo } → globallongouterdeffoo␣  .

nameexpandafter{foo }bar → expandafterfoo␣bar  .

namelet{foo }=bar → letfoo␣=bar  .

namestring{foo } → stringfoo␣  .

namemeaning{foo } → meaningfoo␣  .

While gathering the name of the control sequence token in question, name will trigger expansion of expandable tokens :

defGetCommandName{FooBar}

namenewcommand{GetCommandName}[1]{small I did it!!!}

→ newcommandFooBar[1]{small I did it!!!}

defGetCommandName{CommandNamePartACommandNamePartB}

defCommandNamePartA{Ba}

defCommandNamePartB{rInnerCommandNamePart o}

defInnerCommandNamePart{Fo}

namenewcommand{GetCommandName}{small I did it again!!!}

→ newcommandBarFoo{small I did it again!!!}

You can also nest the calls to name:

Example 1:

   namenameexpandafter{f o o }{b a r }

Processing the first name yields:

   nameexpandafterf␣o␣o␣{b a r }  .

Processing the second name yields:

   expandafterf␣o␣o␣b␣a␣r␣  .

(Analogously: namenamelet{f o o }={b a r } → letf␣o␣o␣=b␣a␣r␣.)

Example 2:

   namenamenameexpandafterexpandafterexpandafter{f o o }expandafter{b a r }{c r a z y }

Processing the first name yields:

   namenameexpandafterexpandafterexpandafterf␣o␣o␣expandafter{b a r }{c r a z y }  .

Processing the second name yields:

   nameexpandafterexpandafterexpandafterf␣o␣o␣expandafterb␣a␣r␣{c r a z y }  .

Processing the third name yields:

   expandafterexpandafterexpandafterf␣o␣o␣expandafterb␣a␣r␣c␣r␣a␣z␣y␣  .

Example 3:

In expansion contexts you can use romannumeral-expansion in order to keep things going.

   romannumeralnamenamename0 expandafterexpandafterexpandafter{f o o }expandafter{b a r }{c r a z y }

romannumeral keeps expanding until it has found some number. In the end it will find the number0 while with non-positive numbers romannumeral will not deliver any token:

   %romannumneral-expansion in progress

   namenamename0 expandafterexpandafterexpandafter{f o o }expandafter{b a r }{c r a z y }

Processing the first name yields:

   %romannumneral-expansion in progress

   namename0 expandafterexpandafterexpandafterf␣o␣o␣expandafter{b a r }{c r a z y }  .

Processing the second name yields:

   %romannumneral-expansion in progress

   name0 expandafterexpandafterexpandafterf␣o␣o␣expandafterb␣a␣r␣{c r a z y }  .

Processing the third name yields:

   %romannumneral-expansion in progress

   0 expandafterexpandafterexpandafterf␣o␣o␣expandafterb␣a␣r␣c␣r␣a␣z␣y␣  .

Now romannumeral finds the number 0. Therefore romannumeral-expansion gets aborted and romannumeral won't deliver any token:

   expandafterexpandafterexpandafterf␣o␣o␣expandafterb␣a␣r␣c␣r␣a␣z␣y␣  .

Be aware that name internally applies csname while

• expansion of expandable tokens takes place while csname during its search for the matching endcsname gathers the character tokens that form the name of the control sequence token in question.




• applying csname as a side effect yields assigning the control sequence in question the meaning of the relax-primitive in case the control sequence in question was undefined before applying csname. That assignment will be restricted to the current scope even if the globaldefs-parameter had a positive value at the time of applying csname.

%%errorcontextlines=1000

documentclass[a4paper]{article}

usepackage{textcomp}%



parindent=0cm

parskip=medskipamount



makeatletter

newcommandname{}%

longdefname#1#{romannumeral0UD@innername{#1}}%

newcommandUD@innername[2]{%

  expandafterUD@exchangeexpandafter{csname#2endcsname}{ #1}%

}%

newcommandUD@exchange[2]{#2#1}%

makeatother





namenewcommand{foo}[2]{%

  Control sequence whose name does not contain any space.\

  Argument 1: textit{textlangle#1textrangle}\

  Argument 2: textit{textlangle#2textrangle}

}%



namenewcommand{foo }[2]{%

  Control sequence whose name has a trailing space.\

  Argument 1: textit{textlangle#1textrangle}\

  Argument 2: textit{textlangle#2textrangle}

}%



namenewcommand{ f o o }[2]{%

  Control sequence whose name is interspersed with spaces.\

  Argument 1: textit{textlangle#1textrangle}\

  Argument 2: textit{textlangle#2textrangle}

}%



newcommand*GetCommandName{CommandNamePartACommandNamePartB}

newcommand*CommandNamePartA{Ba}

newcommand*CommandNamePartB{rInnerCommandNamePart o}

newcommand*InnerCommandNamePart{Fo}

namenewcommand{GetCommandName}{small I did it again!!!}



begin{document}



name{foo}{Arg 1}{Arg 2}



name{foo }{Arg 1}{Arg 2}



name{ f o o }{Arg 1}{Arg 2}



Nesting texttt{stringname}:



nameexpandafternewcommandexpandafter*expandafter{C o N f u SiO n}expandafter{%

  romannumeralnamenamename0 %

  expandafterexpandafterexpandafter{F O O}expandafter{B A R}{C R A Z Y}%

}%

texttt{namestring{C o N f u SiO n} is namemeaning{C o N f u SiO n}}%

\



Playing around with expandable tokens:  



texttt{namestring{GetCommandName}:}

texttt{namemeaning{GetCommandName}}



name{GetCommandName}%



Playing around with grouping:



%Be aware that texttt itself opens up a new scope for typesetting its argument.



%globaldefs=1relax



texttt{%

  begingroupnamestring{w e i r d } is  nameendgroupmeaning{w e i r d }%

}%



texttt{%

  namestring{w e i r d } is  namemeaning{w e i r d }%

}%



end{document}

LaTeX already has a command form that takes the name of a command rather than the csname token:

@namedef{GetCommandName}{small I did it!!!}

should do what you want this is simply expandafterdefcsnameGetCommandNameendcsname{..}