Will Robertson
Will Robertson
Okay, I say chuck this into wherever `l3candidates` ends up and see what people think of it…
Okay, so the most obvious way to look at this is to provide: ``` \group_insert_after:n \group_insert_after:x ``` to match up with the primitive `\group_insert_after:N`. Variations on the code I posted...
> Perhaps having a function to save a value and one to retrieve it may be safer? In that case why not just use a scratch global variable? Would there...
To reignite discussion here I'm going to propose that we implement proposal 3 above. Unless there are objections I'll aim to add this to l3candidates over the next little while.
(Unless of course we decide that it's been ~7 years and no-one really missed the functionality, so drop the suggestion.)
Overnight I realised that the problem EvanAad was having with local functions would have been easily answered using something like ``` \group_after_insert:x { \group_begin: ... setup code ... \group_after_insert:x {...
Sure, I was typing quickly in the above — I definitely wouldn't suggest nesting the \DeclareDocumentCommand in there but rather a more internal command that would be called by \DeclareDocumentCommand....
Due to compatibility reasons we will defer this for xmath.
See also the datatool package — I think the engine of that package would make a good starting point.