Open theseanl opened 1 year ago
Is this actually used in any packages? It seems like it would add a lot of complication to argument parsing...
I am not aware of any real-world use cases, its just that xparse documentation always talks about "tokens", not individual characters, so I figured out that things like r\a{ 1 }
should work and it actually did.
By the way, xparse argument specifications may contain argument processors like > { \SplitArgument { 2 } { , } } m
, which I myself found convenient. I want to support such argument specifications eventually, and then the parsing will need to be more complicated anyway.
The code below should be expanded to
Arg is: 123
.